USHIFT-6887: Fix microshift-low-latency for RHEL10#6590
USHIFT-6887: Fix microshift-low-latency for RHEL10#6590openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
Conversation
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughRPM spec makes TuneD profile installation RHEL-version-aware; tuned profile paths and symlink behavior adjusted. New EL9/EL10 bootc containerfiles add microshift-tuned and write MicroShift/tuned configs. New periodic scenario scripts create a VM, wait for ≥2 boots, then run three ordered Robot test suites with exit-on-failure. Changes
Sequence Diagram(s)sequenceDiagram
participant CI as CI/Test Runner
participant ImageBuilder as Image Builder
participant VMHost as VM Host
participant VM as Test VM
participant Tuned as tuned service
participant MicroShift as MicroShift
CI->>ImageBuilder: build tuned bootc image (EL9/EL10) with microshift-tuned
ImageBuilder-->>CI: tuned image artifact
CI->>VMHost: create VM from tuned image (host1)
VMHost->>VM: boot
VM->>Tuned: apply microshift-baseline profile
Tuned-->>VM: reboot (profile applied)
VM->>CI: report boot entries via journalctl
CI->>CI: wait until >=2 boots (timeout 60s)
CI->>VM: run tuned Robot Framework suites (--exitonfailure)
VM-->>CI: test results
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 11 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (11 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
openshift-ci
Bot
added
the
approved
|
/test ? |
|
/test e2e-aws-tests-bootc-periodic-el10 e2e-aws-tests-bootc-periodic-el9 |
1 similar comment
|
/test e2e-aws-tests-bootc-periodic-el10 e2e-aws-tests-bootc-periodic-el9 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@test/scenarios-bootc/el10/periodics/el102-src`@low-latency.sh:
- Around line 28-39: The loop that polls boots lacks numeric validation and uses
too-short timeout; make boot_num a local variable (local boot_num), validate its
value with a regex like [[ "${boot_num}" =~ ^[0-9]+$ ]] before numeric
comparison, only treat it as >=2 when it passes validation, and extend the
timeout check from 60 to 180 seconds (use start_time and date +%s as in the
existing logic with the updated timeout value). Use run_command_on_vm, boot_num
and start_time to locate the code to change.
In `@test/scenarios-bootc/el9/periodics/el98-src`@low-latency.sh:
- Around line 28-39: The boot-count polling loop using boot_num from
run_command_on_vm can fail if boot_num is empty or non-numeric; change the loop
in which start_time and boot_num are used to first validate boot_num with a
regex (e.g. ^[0-9]+$) before doing the numeric comparison, treating non-matches
as not-yet-ready and continuing the loop; replace the hardcoded 60s timeout with
a configurable TUNED_REBOOT_WAIT_TIMEOUT (default to 180 if unset) and use that
variable in the elapsed-time check; update references to boot_num, start_time
and the loop that contains run_command_on_vm accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: df014366-557b-48e9-b084-bd46f95e85a5
📒 Files selected for processing (4)
test/image-blueprints-bootc/el10/layer3-periodic/group1/rhel102-bootc-source-tuned.containerfiletest/image-blueprints-bootc/el9/layer3-periodic/group1/rhel98-bootc-source-tuned.containerfiletest/scenarios-bootc/el10/periodics/el102-src@low-latency.shtest/scenarios-bootc/el9/periodics/el98-src@low-latency.sh
| local -r start_time=$(date +%s) | ||
| while true; do | ||
| boot_num=$(run_command_on_vm host1 "sudo journalctl --list-boots --quiet | wc -l" || true) | ||
| boot_num="${boot_num%$'\r'*}" | ||
| if [[ "${boot_num}" -ge 2 ]]; then | ||
| break | ||
| fi | ||
| if [ $(( $(date +%s) - start_time )) -gt 60 ]; then | ||
| echo "Timed out waiting for VM having 2 boots" | ||
| exit 1 | ||
| fi | ||
| sleep 5 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Read the specific file and check lines around 28-39
cat -n "test/scenarios-bootc/el10/periodics/el102-src@low-latency.sh" | sed -n '20,45p'Repository: openshift/microshift
Length of output: 1062
🏁 Script executed:
# Search for similar boot-polling patterns to understand the "hardening" mentioned
rg "boot_num|list-boots" --type sh -B 3 -A 3Repository: openshift/microshift
Length of output: 10872
🏁 Script executed:
# Search for TUNED_REBOOT_WAIT_TIMEOUT to see if it's used elsewhere
rg "TUNED_REBOOT_WAIT_TIMEOUT" --type shRepository: openshift/microshift
Length of output: 46
🏁 Script executed:
# Search for boot_num with regex validation (the hardening pattern)
rg 'boot_num.*=~|boot_num.*\[0-9\]' --type sh -B 2 -A 2Repository: openshift/microshift
Length of output: 46
🏁 Script executed:
# Search for longer timeout values in similar context
rg 'boot_wait_timeout|TUNED_REBOOT_WAIT_TIMEOUT|boot.*timeout.*18[0-9]|boot.*timeout.*2[0-9]{2}' --type sh -B 3 -A 3Repository: openshift/microshift
Length of output: 46
🏁 Script executed:
# Look for helper functions or common boot polling patterns
rg 'wait.*boot|boot.*poll' --type sh -iRepository: openshift/microshift
Length of output: 3821
🏁 Script executed:
# Check if there are any helper functions related to boot polling
rg 'run_command_on_vm' --type sh -A 5 | head -50Repository: openshift/microshift
Length of output: 4035
🏁 Script executed:
# Look at the test/bin/scenario.sh to see if there's a better pattern
cat test/bin/scenario.sh | head -100Repository: openshift/microshift
Length of output: 3645
🏁 Script executed:
# Check if there are any recent commits or patterns with numeric validation
rg '\[0-9\]\+|\^\[0-9\]' --type sh -B 2 -A 2 | head -40Repository: openshift/microshift
Length of output: 3239
Harden boot-polling to prevent CI flakes.
The current code lacks numeric validation for boot_num (can fail with non-numeric output during reboots) and uses a 60-second timeout that's too tight for periodic environments. Add regex validation (^[0-9]+$), increase timeout to 180 seconds, and declare boot_num as local.
Proposed fix
scenario_run_tests() {
exit_if_image_not_found "${start_image}"
# Should not be run immediately after creating VM because of
# microshift-tuned rebooting the node to activate the profile.
local -r start_time=$(date +%s)
+ local -r boot_wait_timeout="${TUNED_REBOOT_WAIT_TIMEOUT:-180}"
while true; do
- boot_num=$(run_command_on_vm host1 "sudo journalctl --list-boots --quiet | wc -l" || true)
+ local boot_num
+ boot_num=$(run_command_on_vm host1 "sudo journalctl --list-boots --quiet | wc -l" 2>/dev/null || true)
boot_num="${boot_num%$'\r'*}"
- if [[ "${boot_num}" -ge 2 ]]; then
+ if [[ "${boot_num}" =~ ^[0-9]+$ ]] && [[ "${boot_num}" -ge 2 ]]; then
break
fi
- if [ $(( $(date +%s) - start_time )) -gt 60 ]; then
+ if [ $(( $(date +%s) - start_time )) -gt "${boot_wait_timeout}" ]; then
echo "Timed out waiting for VM having 2 boots"
exit 1
fi
sleep 5
done📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| local -r start_time=$(date +%s) | |
| while true; do | |
| boot_num=$(run_command_on_vm host1 "sudo journalctl --list-boots --quiet | wc -l" || true) | |
| boot_num="${boot_num%$'\r'*}" | |
| if [[ "${boot_num}" -ge 2 ]]; then | |
| break | |
| fi | |
| if [ $(( $(date +%s) - start_time )) -gt 60 ]; then | |
| echo "Timed out waiting for VM having 2 boots" | |
| exit 1 | |
| fi | |
| sleep 5 | |
| local -r start_time=$(date +%s) | |
| local -r boot_wait_timeout="${TUNED_REBOOT_WAIT_TIMEOUT:-180}" | |
| while true; do | |
| local boot_num | |
| boot_num=$(run_command_on_vm host1 "sudo journalctl --list-boots --quiet | wc -l" 2>/dev/null || true) | |
| boot_num="${boot_num%$'\r'*}" | |
| if [[ "${boot_num}" =~ ^[0-9]+$ ]] && [[ "${boot_num}" -ge 2 ]]; then | |
| break | |
| fi | |
| if [ $(( $(date +%s) - start_time )) -gt "${boot_wait_timeout}" ]; then | |
| echo "Timed out waiting for VM having 2 boots" | |
| exit 1 | |
| fi | |
| sleep 5 | |
| done |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@test/scenarios-bootc/el10/periodics/el102-src`@low-latency.sh around lines 28
- 39, The loop that polls boots lacks numeric validation and uses too-short
timeout; make boot_num a local variable (local boot_num), validate its value
with a regex like [[ "${boot_num}" =~ ^[0-9]+$ ]] before numeric comparison,
only treat it as >=2 when it passes validation, and extend the timeout check
from 60 to 180 seconds (use start_time and date +%s as in the existing logic
with the updated timeout value). Use run_command_on_vm, boot_num and start_time
to locate the code to change.
| local -r start_time=$(date +%s) | ||
| while true; do | ||
| boot_num=$(run_command_on_vm host1 "sudo journalctl --list-boots --quiet | wc -l" || true) | ||
| boot_num="${boot_num%$'\r'*}" | ||
| if [[ "${boot_num}" -ge 2 ]]; then | ||
| break | ||
| fi | ||
| if [ $(( $(date +%s) - start_time )) -gt 60 ]; then | ||
| echo "Timed out waiting for VM having 2 boots" | ||
| exit 1 | ||
| fi | ||
| sleep 5 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Verify the current code pattern in both low-latency scenario files.
for f in \
test/scenarios-bootc/el9/periodics/el98-src@low-latency.sh \
test/scenarios-bootc/el10/periodics/el102-src@low-latency.sh
do
echo "== ${f} =="
rg -n 'boot_num=.*journalctl|"\$\{boot_num\}" -ge 2| -gt 60' "${f}"
done
# Reproduce bash integer-compare behavior with empty value.
bash -lc 'boot_num=""; if [[ "${boot_num}" -ge 2 ]]; then echo "ok"; fi' || trueRepository: openshift/microshift
Length of output: 735
Harden boot-count polling to prevent flaky failures.
The [[ "${boot_num}" -ge 2 ]] comparison fails when boot_num is empty or non-numeric during reboots. The hardcoded 60s timeout is also brittle for CI environments. Add regex validation before numeric comparison and use a configurable timeout via TUNED_REBOOT_WAIT_TIMEOUT environment variable (default 180s).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@test/scenarios-bootc/el9/periodics/el98-src`@low-latency.sh around lines 28 -
39, The boot-count polling loop using boot_num from run_command_on_vm can fail
if boot_num is empty or non-numeric; change the loop in which start_time and
boot_num are used to first validate boot_num with a regex (e.g. ^[0-9]+$) before
doing the numeric comparison, treating non-matches as not-yet-ready and
continuing the loop; replace the hardcoded 60s timeout with a configurable
TUNED_REBOOT_WAIT_TIMEOUT (default to 180 if unset) and use that variable in the
elapsed-time check; update references to boot_num, start_time and the loop that
contains run_command_on_vm accordingly.
|
/test e2e-aws-tests-bootc-periodic-el10 e2e-aws-tests-bootc-periodic-el9 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packaging/rpm/microshift.spec`:
- Around line 19-24: get_profile_path in packaging/tuned/microshift-tuned.py
currently only checks /etc/tuned/{profile} and /usr/lib/tuned/{profile}; update
this function to also check /usr/lib/tuned/profiles/{profile} (the relocated
EL10 profile path) so that when the spec installs profiles to
/usr/lib/tuned/profiles/microshift-baseline the function will find them; modify
the search_paths list/logic inside get_profile_path() to include the new path
before failing.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: e557f24e-6d40-4741-b231-ac3310b6ca1e
📒 Files selected for processing (5)
packaging/rpm/microshift.spectest/image-blueprints-bootc/el10/layer3-periodic/group1/rhel102-bootc-source-tuned.containerfiletest/image-blueprints-bootc/el9/layer3-periodic/group1/rhel98-bootc-source-tuned.containerfiletest/scenarios-bootc/el10/periodics/el102-src@low-latency.shtest/scenarios-bootc/el9/periodics/el98-src@low-latency.sh
✅ Files skipped from review due to trivial changes (1)
- test/image-blueprints-bootc/el10/layer3-periodic/group1/rhel102-bootc-source-tuned.containerfile
🚧 Files skipped from review as they are similar to previous changes (3)
- test/scenarios-bootc/el10/periodics/el102-src@low-latency.sh
- test/scenarios-bootc/el9/periodics/el98-src@low-latency.sh
- test/image-blueprints-bootc/el9/layer3-periodic/group1/rhel98-bootc-source-tuned.containerfile
|
/test e2e-aws-tests-bootc-periodic-el10 e2e-aws-tests-bootc-periodic-el9 |
There was a problem hiding this comment.
♻️ Duplicate comments (1)
packaging/tuned/microshift-tuned.py (1)
121-122:⚠️ Potential issue | 🔴 CriticalMissing comma makes EL10 profile path unreachable
At Line 121 and Line 122, the two adjacent f-strings are concatenated into one invalid path, so
/usr/lib/tuned/profiles/{profile}is never checked.Proposed fix
paths = [ f"/etc/tuned/{profile}", f"/etc/tuned/profiles/{profile}", - f"/usr/lib/tuned/{profile}" - f"/usr/lib/tuned/profiles/{profile}" + f"/usr/lib/tuned/{profile}", + f"/usr/lib/tuned/profiles/{profile}", ]#!/bin/bash set -euo pipefail echo "Inspect get_profile_path list entries:" rg -n -A10 'def get_profile_path' packaging/tuned/microshift-tuned.py echo echo "Verify both /usr/lib/tuned entries are separate comma-terminated list items:" rg -nP 'f"/usr/lib/tuned/\{profile\}",\s*$' packaging/tuned/microshift-tuned.py rg -nP 'f"/usr/lib/tuned/profiles/\{profile\}",\s*$' packaging/tuned/microshift-tuned.py🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packaging/tuned/microshift-tuned.py` around lines 121 - 122, In get_profile_path, two adjacent f-strings for "/usr/lib/tuned/{profile}" and "/usr/lib/tuned/profiles/{profile}" were accidentally concatenated because a comma was missing; fix by adding a comma between those two list entries so both paths are separate list items (locate the f-strings in get_profile_path and insert the missing comma to ensure "/usr/lib/tuned/profiles/{profile}" is checked).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@packaging/tuned/microshift-tuned.py`:
- Around line 121-122: In get_profile_path, two adjacent f-strings for
"/usr/lib/tuned/{profile}" and "/usr/lib/tuned/profiles/{profile}" were
accidentally concatenated because a comma was missing; fix by adding a comma
between those two list entries so both paths are separate list items (locate the
f-strings in get_profile_path and insert the missing comma to ensure
"/usr/lib/tuned/profiles/{profile}" is checked).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: fddcba34-60b4-4372-ab58-f49c4a98fb86
📒 Files selected for processing (6)
packaging/rpm/microshift.specpackaging/tuned/microshift-tuned.pytest/image-blueprints-bootc/el10/layer3-periodic/group1/rhel102-bootc-source-tuned.containerfiletest/image-blueprints-bootc/el9/layer3-periodic/group1/rhel98-bootc-source-tuned.containerfiletest/scenarios-bootc/el10/periodics/el102-src@low-latency.shtest/scenarios-bootc/el9/periodics/el98-src@low-latency.sh
🚧 Files skipped from review as they are similar to previous changes (4)
- test/image-blueprints-bootc/el9/layer3-periodic/group1/rhel98-bootc-source-tuned.containerfile
- test/scenarios-bootc/el9/periodics/el98-src@low-latency.sh
- test/scenarios-bootc/el10/periodics/el102-src@low-latency.sh
- test/image-blueprints-bootc/el10/layer3-periodic/group1/rhel102-bootc-source-tuned.containerfile
pmtk
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@pmtk: This pull request references USHIFT-6887 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
RHEL10 uses different path for the profiles, so while we're still using RHEL9 for the builders, we need a workaround to make the package usage on both systems
|
/test e2e-aws-tests-bootc-periodic-el10 e2e-aws-tests-bootc-periodic-el9 |
There was a problem hiding this comment.
♻️ Duplicate comments (1)
test/scenarios-bootc/el9/periodics/el98-src@low-latency.sh (1)
28-39:⚠️ Potential issue | 🟠 MajorHarden boot polling against non-numeric output and make timeout configurable.
Line 32 can fail whenboot_numis empty/non-numeric during reboot windows, and Line 35’s fixed60seconds is brittle in CI.Proposed patch
- local -r start_time=$(date +%s) + local -r start_time=$(date +%s) + local -r reboot_wait_timeout="${TUNED_REBOOT_WAIT_TIMEOUT:-180}" + local boot_num while true; do boot_num=$(run_command_on_vm host1 "sudo journalctl --list-boots --quiet | wc -l" || true) boot_num="${boot_num%$'\r'*}" - if [[ "${boot_num}" -ge 2 ]]; then + if [[ "${boot_num}" =~ ^[0-9]+$ ]] && [[ "${boot_num}" -ge 2 ]]; then break fi - if [ $(( $(date +%s) - start_time )) -gt 60 ]; then - echo "Timed out waiting for VM having 2 boots" + if [ $(( $(date +%s) - start_time )) -gt "${reboot_wait_timeout}" ]; then + echo "Timed out waiting for VM having 2 boots (timeout: ${reboot_wait_timeout}s)" exit 1 fi sleep 5 done#!/bin/bash set -euo pipefail # Verify current pattern in both EL9/EL10 low-latency scenarios. for f in \ test/scenarios-bootc/el9/periodics/el98-src@low-latency.sh \ test/scenarios-bootc/el10/periodics/el102-src@low-latency.sh do echo "== ${f} ==" rg -n -C2 'boot_num=.*journalctl|"\$\{boot_num\}" -ge 2| -gt 60|TUNED_REBOOT_WAIT_TIMEOUT' "${f}" || true done # Reproduce bash behavior with empty value in numeric compare. bash -lc 'boot_num=""; if [[ "${boot_num}" -ge 2 ]]; then echo "ok"; fi' || true🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@test/scenarios-bootc/el9/periodics/el98-src`@low-latency.sh around lines 28 - 39, Replace the brittle numeric compare and hard-coded timeout: validate that boot_num (set by run_command_on_vm host1) is numeric before comparing (e.g., use a regex like ^[0-9]+$ or bash arithmetic with a safe check) and only treat it as >=2 when numeric; also make the timeout configurable by introducing a TUNED_REBOOT_WAIT_TIMEOUT (default 60) used in the elapsed-time check instead of the hard-coded 60, and keep the existing carriage-return strip for boot_num to avoid spurious non-numeric characters.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@test/scenarios-bootc/el9/periodics/el98-src`@low-latency.sh:
- Around line 28-39: Replace the brittle numeric compare and hard-coded timeout:
validate that boot_num (set by run_command_on_vm host1) is numeric before
comparing (e.g., use a regex like ^[0-9]+$ or bash arithmetic with a safe check)
and only treat it as >=2 when numeric; also make the timeout configurable by
introducing a TUNED_REBOOT_WAIT_TIMEOUT (default 60) used in the elapsed-time
check instead of the hard-coded 60, and keep the existing carriage-return strip
for boot_num to avoid spurious non-numeric characters.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: 6036c903-31aa-43b9-ab87-a1c6f8d955d8
📒 Files selected for processing (6)
packaging/rpm/microshift.specpackaging/tuned/microshift-tuned.pytest/image-blueprints-bootc/el10/layer3-periodic/group1/rhel102-bootc-source-tuned.containerfiletest/image-blueprints-bootc/el9/layer3-periodic/group1/rhel98-bootc-source-tuned.containerfiletest/scenarios-bootc/el10/periodics/el102-src@low-latency.shtest/scenarios-bootc/el9/periodics/el98-src@low-latency.sh
✅ Files skipped from review due to trivial changes (1)
- packaging/tuned/microshift-tuned.py
🚧 Files skipped from review as they are similar to previous changes (2)
- test/image-blueprints-bootc/el10/layer3-periodic/group1/rhel102-bootc-source-tuned.containerfile
- test/scenarios-bootc/el10/periodics/el102-src@low-latency.sh
|
/test e2e-aws-tests-bootc-periodic-el10 e2e-aws-tests-bootc-periodic-el9 |
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: agullon, pmtk The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/verified by CI |
|
/cherrypick release-4.22 |
openshift-ci-robot
added
the
verified
|
@agullon: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@agullon: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@agullon: new pull request created: #6614 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
4 participants
RHEL10 uses different path for the profiles, so while we're still using RHEL9 for the builders, we need a workaround to make the package usage on both systems
Summary by CodeRabbit
Refactor
New Features