USHIFT-6716: Add el10 bootc release scenarios#6401
Merged
openshift-merge-bot[bot] merged 7 commits intoopenshift:mainfrom Apr 9, 2026
Merged
USHIFT-6716: Add el10 bootc release scenarios#6401openshift-merge-bot[bot] merged 7 commits intoopenshift:mainfrom
openshift-merge-bot[bot] merged 7 commits intoopenshift:mainfrom
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@vanhalenar: This pull request references USHIFT-6716 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 task to target the "4.22.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. |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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:
WalkthroughThis pull request introduces three new BootC container build definitions and replaces two existing release scenario scripts with 26 new scenario scripts across various release configurations (FIPS, IPv6, upgrade paths, multi-config, tuned profiles). The containerfiles define build steps for MicroShift RPM installation and system configuration; the scenario scripts orchestrate VM lifecycle and test execution workflows. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~40 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Contributor
Author
|
/test ? |
Contributor
Author
|
/test e2e-aws-tests-bootc-release-el10 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 9
🧹 Nitpick comments (1)
test/scenarios-bootc/el10/releases/el102-lrel@ipv6.sh (1)
21-28: Harden restoration ofMIRROR_REGISTRY_URLon early exit.If the function exits between Line 22 and Line 28, the overridden global can leak to later steps. Use a trap for guaranteed restore.
Proposed hardening
- local original_mirror_registry_url="${MIRROR_REGISTRY_URL}" - MIRROR_REGISTRY_URL="$(hostname):${MIRROR_REGISTRY_PORT}/microshift" + local original_mirror_registry_url="${MIRROR_REGISTRY_URL}" + trap 'MIRROR_REGISTRY_URL="${original_mirror_registry_url}"' RETURN + MIRROR_REGISTRY_URL="$(hostname):${MIRROR_REGISTRY_PORT}/microshift" @@ - # Restore original MIRROR_REGISTRY_URL for runtime use - MIRROR_REGISTRY_URL="${original_mirror_registry_url}" + # restored by trap on function return🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@test/scenarios-bootc/el10/releases/el102-lrel`@ipv6.sh around lines 21 - 28, The MIRROR_REGISTRY_URL override can leak if the script exits early; before setting MIRROR_REGISTRY_URL="$(hostname):${MIRROR_REGISTRY_PORT}/microshift" save the original in original_mirror_registry_url and install a trap on EXIT that restores MIRROR_REGISTRY_URL="${original_mirror_registry_url}" and clears the trap, then call prepare_kickstart (function name) and finally explicitly restore and remove the trap after the call to avoid double-restores—this guarantees the global is restored on any early exit.
🤖 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/image-blueprints-bootc/layer4-release/group1/rhel102-bootc-brew-nightly-with-optional.containerfile`:
- Around line 13-14: The containerfile COPY references
microshift-fast-datapath-rhel9.repo while building an EL10 image; create a
microshift-fast-datapath-rhel10.repo with the EL10 repository definitions and
replace references to microshift-fast-datapath-rhel9.repo in all EL10
containerfiles (or, if reuse is intentional, add documentation/comments
explaining why the EL9 repo is compatible) so that the COPY line and package
streams use an EL10-specific fast-datapath repo.
In `@test/scenarios-bootc/el10/releases/el102-lrel`@fips.sh:
- Around line 7-12: The check_platform function currently hardcodes record_junit
"setup" which misreports skips when invoked from other hooks; modify
check_platform to accept a hook identifier parameter (e.g., check_platform
"$HOOK_NAME") and use that parameter in the record_junit call instead of the
hardcoded "setup", and update all call sites (the places invoking check_platform
from teardown/test hooks) to pass the correct hook string (for example
"teardown" or "test" combined with "scenario_create_vms") so the recorded JUnit
entry matches the actual hook context.
In `@test/scenarios-bootc/el10/releases/el102-lrel`@iso-standard1.sh:
- Line 11: Replace the incorrect use of the source image variable start_image
when calling launch_vm with the intended VM profile name: change the call
launch_vm "${start_image}" --vm_vcpus 4 to launch_vm rhel102-bootc --vm_vcpus 4
so the VM uses the rhel102-bootc profile; apply the same fix in the sibling
script el102-lrel@iso-standard2.sh where launch_vm is passed start_image.
In `@test/scenarios-bootc/el10/releases/el102-lrel`@iso-standard2.sh:
- Line 11: The call to launch_vm is using the source image variable start_image
but must pass the boot blueprint name; change the first argument of launch_vm
from ${start_image} to the boot profile name rhel102-bootc (keeping the existing
--vm_vcpus 4 flag) so launch_vm("rhel102-bootc", ...) is invoked and the correct
target is provisioned.
In `@test/scenarios-bootc/el10/releases/el102-lrel`@multi-config-standard1.sh:
- Around line 21-22: The image-check logic in scenario_create_vms is
inconsistent with the standard2 variant: it calls exit_if_image_not_found (hard
fail) while the other script uses does_image_exist (soft skip); pick the
intended behavior and make both scripts match—either replace
exit_if_image_not_found with does_image_exist in scenario_create_vms to perform
a soft skip, or change the other script to use exit_if_image_not_found for a
hard failure; update the call in scenario_create_vms and any related
documentation/comments so both variants use the same image-checking function
(exit_if_image_not_found or does_image_exist).
In `@test/scenarios-bootc/el10/releases/el102-lrel`@multi-config-standard2.sh:
- Around line 96-102: The comment "Validate LVMS still works after all tests" is
misleading because the run_command_on_vm call to execute
scripts/lvms-helpers/checkWorkloadExists.sh runs before run_tests; either move
the two lines that invoke checkWorkloadExists.sh and cleanupWorkload.sh (the
run_command_on_vm host1 'bash -s' invocations) to after the run_tests invocation
so validation truly occurs post-tests, or update the echo/comment text to
accurately state this is a pre-test validation; locate these calls by the
run_command_on_vm usage and the referenced scripts checkWorkloadExists.sh and
cleanupWorkload.sh and adjust accordingly.
In `@test/scenarios-bootc/el10/releases/el102-lrel`@multi-nic.sh:
- Around line 25-26: The script extracts NIC IPs using head/tail which can pick
the wrong addresses when manage-vm.sh ip returns more or fewer entries; change
the logic that sets vm_ip1 and vm_ip2 to select by interface/network name (e.g.,
call "${ROOTDIR}/scripts/devenv-builder/manage-vm.sh" ip -n "${vmname}" <ifname>
or parse the output to find entries matching the desired interface labels) and
validate the returned list has exactly the expected IPs before calling
run_tests; update the assignments for vm_ip1 and vm_ip2 and add a guard that
errors out with a clear message if the expected addresses are not found for
vmname.
In `@test/scenarios-bootc/el10/releases/el98-lrel`@el102-lrel@standard1.sh:
- Line 17: The VM launch target in the launch_vm invocation is wrong: replace
the image identifier used in the launch_vm command (currently "rhel96-bootc")
with the EL9.8 start image identifier (e.g., "rhel98-bootc") so the VM profile
matches the declared EL9.8 start image; update the single call to launch_vm
rhel96-bootc --vm_vcpus 4 to use the EL9.8 image name instead.
In `@test/scenarios-bootc/el10/releases/el98-lrel`@el102-lrel@standard2.sh:
- Line 17: The launch call uses the wrong base image: replace the launch_vm
invocation that currently specifies "rhel96-bootc" with the EL9.8 base image
"rhel98-bootc" so the scenario tests the correct upgrade path; update the single
invocation of launch_vm (the line containing launch_vm rhel96-bootc) to use
rhel98-bootc.
---
Nitpick comments:
In `@test/scenarios-bootc/el10/releases/el102-lrel`@ipv6.sh:
- Around line 21-28: The MIRROR_REGISTRY_URL override can leak if the script
exits early; before setting
MIRROR_REGISTRY_URL="$(hostname):${MIRROR_REGISTRY_PORT}/microshift" save the
original in original_mirror_registry_url and install a trap on EXIT that
restores MIRROR_REGISTRY_URL="${original_mirror_registry_url}" and clears the
trap, then call prepare_kickstart (function name) and finally explicitly restore
and remove the trap after the call to avoid double-restores—this guarantees the
global is restored on any early exit.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: 234be6cf-4d6a-4d72-8261-a0a977b95f69
📒 Files selected for processing (29)
test/image-blueprints-bootc/layer4-release/group1/rhel102-bootc-brew-nightly-with-optional.containerfiletest/image-blueprints-bootc/layer4-release/group2/rhel102-bootc-brew-lrel-fips.containerfiletest/image-blueprints-bootc/layer4-release/group2/rhel102-bootc-brew-lrel-tuned.containerfiletest/scenarios-bootc/el10/releases/el102-lrel@ai-model-serving-online.shtest/scenarios-bootc/el10/releases/el102-lrel@configuration.shtest/scenarios-bootc/el10/releases/el102-lrel@dual-stack.shtest/scenarios-bootc/el10/releases/el102-lrel@fips.shtest/scenarios-bootc/el10/releases/el102-lrel@ipv6.shtest/scenarios-bootc/el10/releases/el102-lrel@iso-standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@iso-standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@low-latency.shtest/scenarios-bootc/el10/releases/el102-lrel@multi-config-standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@multi-config-standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@multi-nic.shtest/scenarios-bootc/el10/releases/el102-lrel@nightly-brew-standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@nightly-brew-standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@osconfig-router.shtest/scenarios-bootc/el10/releases/el102-lrel@published-images-standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@published-images-standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@storage-telemetry.shtest/scenarios-bootc/el10/releases/el102-lrel@tlsv13-standard1.shtest/scenarios-bootc/el10/releases/el96-y2@el102-lrel@lvms.shtest/scenarios-bootc/el10/releases/el96-y2@el102-lrel@standard1.shtest/scenarios-bootc/el10/releases/el96-y2@el102-lrel@standard2.shtest/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@lvms.shtest/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard1.shtest/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard2.sh
💤 Files with no reviewable changes (2)
- test/scenarios-bootc/el10/releases/el102-lrel@standard2.sh
- test/scenarios-bootc/el10/releases/el102-lrel@standard1.sh
Contributor
Author
|
/test e2e-aws-tests-bootc-release-el10 |
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 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/releases/el102-lrel`@tlsv13-standard2.sh:
- Around line 14-18: The teardown function scenario_remove_vms should not be
gated by registry/image checks: remove or relocate the call to
exit_if_image_not_found so it cannot prevent remove_vm host1 from running;
specifically, either delete the exit_if_image_not_found "${start_image}" line
from scenario_remove_vms or change it to a non-fatal check/log (e.g., warn) so
that remove_vm host1 always executes to avoid leaked VMs.
In `@test/scenarios-bootc/el10/releases/el96-y1`@el102-lrel@lvms.sh:
- Around line 20-23: The teardown function scenario_remove_vms currently calls
exit_if_image_not_found("${start_image}") and
exit_if_image_not_found("${dest_image}") which can abort the teardown and leave
host1 running; change the logic so image-not-found checks do not call exit
during teardown (either remove these exit_* calls from scenario_remove_vms or
replace them with non-fatal checks that log a warning), and ensure remove_vm
host1 is always executed unconditionally at the end of scenario_remove_vms so
the VM is always cleaned up even if image lookups fail.
- Around line 42-55: The retry counter `iter` in checkLvmsResources.sh is
initialized once before the "for pod in" loop so all pods share retries; move
the initialization (iter=24) inside the loop so each pod starts with its own
retry budget, i.e., locate the "for pod in" loop in checkLvmsResources.sh and
add/reset iter=24 at the top of that loop body (before the per-pod retry/wait
logic) to ensure each pod gets independent retries.
In `@test/scenarios-bootc/el10/releases/el96-y1`@el102-lrel@standard1.sh:
- Around line 20-25: The teardown function scenario_remove_vms must not abort
based on image lookup; remove or relocate the exit_if_image_not_found calls so
VM cleanup always runs — ensure scenario_remove_vms calls remove_vm host1
unconditionally (or only guards that don't call exit), and if image validation
is still needed keep it in setup code instead of inside scenario_remove_vms.
🪄 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), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: d1b8e79b-c036-4cd6-bd7a-d86c3d378d48
📒 Files selected for processing (6)
test/scenarios-bootc/el10/releases/el102-lrel@tlsv13-standard2.shtest/scenarios-bootc/el10/releases/el96-y1@el102-lrel@lvms.shtest/scenarios-bootc/el10/releases/el96-y1@el102-lrel@standard1.shtest/scenarios-bootc/el10/releases/el96-y1@el102-lrel@standard2.shtest/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard1.shtest/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard2.sh
🚧 Files skipped from review as they are similar to previous changes (2)
- test/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard1.sh
- test/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard2.sh
Contributor
Author
|
/test e2e-aws-tests-bootc-release-el10 |
Contributor
|
/retest |
Contributor
Author
|
/test e2e-aws-tests-bootc-arm-el9 |
Contributor
|
/test e2e-aws-tests-bootc-release-el10 Added by microshift-prow-jobs-for-pull-requests.sh 🤖 |
vanhalenar
force-pushed
the
el10-release-scenarios
branch
from
f8774b2 to
8286617
Compare
Contributor
Author
|
/test e2e-aws-tests-bootc-release-el10 |
There was a problem hiding this comment.
Actionable comments posted: 8
🤖 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/image-blueprints-bootc/layer4-release/group1/rhel102-bootc-brew-nightly-with-optional.containerfile`:
- Around line 6-10: The ARG USHIFT_RPM_REPO_PATH=/tmp/$USHIFT_RPM_REPO_NAME does
not expand and will be literal; replace usages by either defining the path with
an ENV that expands (e.g. ENV USHIFT_RPM_REPO_PATH=/tmp/$USHIFT_RPM_REPO_NAME)
or avoid the ARG entirely and use the expanded variable directly in COPY and
cleanup commands (e.g. COPY ./rpm-repos/${USHIFT_RPM_REPO_NAME}
/tmp/${USHIFT_RPM_REPO_NAME}) so that the COPY (symbol: COPY) and the later
cleanup lines that reference USHIFT_RPM_REPO_PATH target the actual
/tmp/microshift-brew directory instead of a literal $USHIFT_RPM_REPO_NAME
string.
- Around line 20-29: The templated RPM ranges (MICROSHIFT_MANDATORY_RPMS,
MICROSHIFT_OPTIONAL_RPMS, MICROSHIFT_X86_64_RPMS) can emit empty tokens when
splitting by space, producing invalid items like "-{{ env.Getenv
"BREW_NIGHTLY_RELEASE_VERSION" }}"; inside each range (the {{ range (env.Getenv
"...") | strings.Split " " -}} blocks) guard the iteration by wrapping the
emitted line with a conditional check (e.g. {{ if ne . "" }} ... {{ end }}) so
only non-empty entries produce the "{{ . }}-{{ env.Getenv
"BREW_NIGHTLY_RELEASE_VERSION" }}" output, and apply this to all three ranges
including the x86_64 branch.
In
`@test/image-blueprints-bootc/layer4-release/group2/rhel102-bootc-brew-lrel-tuned.containerfile`:
- Line 17: The tuned profile currently hard-codes CPU sets via
reservedSystemCPUs (= 0-1) and the other entries on lines 39-43; replace these
fixed topology values with configurable variables (e.g., ARG or ENV placeholders
such as RESERVED_SYSTEM_CPUS, KUBELET_CPUS, RT_CPUS) and use those placeholders
in the tuned containerfile so the values can be supplied per-scenario; if
possible provide a safe default that auto-computes based on detected CPU count
(or leaves the field empty) to avoid assuming specific core layouts, and update
the containerfile’s ARG/ENV documentation so callers can supply the correct
CPU-set strings for different instance sizes.
In `@test/scenarios-bootc/el10/releases/el102-lrel`@ipv6.sh:
- Around line 14-30: The preflight currently validates "${start_image}" via
exit_if_image_not_found but then calls launch_vm with a hardcoded VM name
"rhel102-bootc", so a missing VM image there will only fail at launch; add a
check before launch_vm to validate the actual image/name used by launch_vm
(either call exit_if_image_not_found "rhel102-bootc" or replace the literal with
a variable like vm_image and validate exit_if_image_not_found "${vm_image}") so
the precheck aligns with launch_vm.
- Around line 33-36: The cleanup function scenario_remove_vms currently calls
exit_if_image_not_found which can abort the function before remove_vm host1
runs; change the flow so VM cleanup always runs even if the image check
fails—either move remove_vm host1 before calling exit_if_image_not_found, or
replace the fatal helper with a non-fatal check (e.g., warn_if_image_not_found
or an if/else that logs but does not exit) inside scenario_remove_vms so that
remove_vm host1 is executed on cleanup regardless of image lookup result.
In `@test/scenarios-bootc/el10/releases/el102-lrel`@multi-config-standard2.sh:
- Around line 22-35: The precheck validates "${start_image}" but the VM is
launched as "rhel102-bootc", causing a mismatch; update the precheck to validate
the same image used by launch_vm by either calling exit_if_image_not_found with
the image identifier passed to launch_vm (ensure the same variable is used) or
set start_image to the image variable/name used in launch_vm so
exit_if_image_not_found and launch_vm reference the identical symbol
(references: exit_if_image_not_found, start_image, launch_vm rhel102-bootc).
- Around line 38-41: The teardown function scenario_remove_vms currently calls
exit_if_image_not_found "${start_image}" which can abort and prevent remove_vm
host1 from running; change scenario_remove_vms so teardown is best-effort by
removing the exit_if_image_not_found call (or moving that image existence check
to setup code) and always invoking remove_vm host1 (and any other teardown
actions) regardless of image availability; update references in the file to keep
image validation only in setup paths, not in scenario_remove_vms.
In `@test/scenarios-bootc/el10/releases/el102-lrel`@storage-telemetry.sh:
- Around line 23-28: The telemetry run invocation using the run_tests host1 call
passes PROXY_HOST, PROXY_PORT and PROMETHEUS_HOST but omits PROMETHEUS_PORT
which telemetry.robot expects non-empty; update the run_tests call (the
run_tests host1 invocation) to include --variable
"PROMETHEUS_PORT:<port_or_env_value>" alongside the existing variables so
telemetry.robot receives a non-empty PROMETHEUS_PORT (use the proper port value
or substitute an env var like ${PROMETHEUS_PORT} consistent with how
PROXY_HOST/PROXY_PORT are provided).
🪄 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), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: ec77d69b-b688-4709-a386-a803f366c75b
📒 Files selected for processing (33)
test/image-blueprints-bootc/layer4-release/group1/rhel102-bootc-brew-nightly-with-optional.containerfiletest/image-blueprints-bootc/layer4-release/group2/rhel102-bootc-brew-lrel-fips.containerfiletest/image-blueprints-bootc/layer4-release/group2/rhel102-bootc-brew-lrel-tuned.containerfiletest/scenarios-bootc/el10/releases/el102-lrel@ai-model-serving-online.shtest/scenarios-bootc/el10/releases/el102-lrel@configuration.shtest/scenarios-bootc/el10/releases/el102-lrel@dual-stack.shtest/scenarios-bootc/el10/releases/el102-lrel@fips.shtest/scenarios-bootc/el10/releases/el102-lrel@ipv6.shtest/scenarios-bootc/el10/releases/el102-lrel@iso-standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@iso-standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@low-latency.shtest/scenarios-bootc/el10/releases/el102-lrel@multi-config-standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@multi-config-standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@multi-nic.shtest/scenarios-bootc/el10/releases/el102-lrel@nightly-brew-standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@nightly-brew-standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@osconfig-router.shtest/scenarios-bootc/el10/releases/el102-lrel@published-images-standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@published-images-standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@standard2.shtest/scenarios-bootc/el10/releases/el102-lrel@storage-telemetry.shtest/scenarios-bootc/el10/releases/el102-lrel@tlsv13-standard1.shtest/scenarios-bootc/el10/releases/el102-lrel@tlsv13-standard2.shtest/scenarios-bootc/el10/releases/el96-y1@el102-lrel@lvms.shtest/scenarios-bootc/el10/releases/el96-y1@el102-lrel@standard1.shtest/scenarios-bootc/el10/releases/el96-y1@el102-lrel@standard2.shtest/scenarios-bootc/el10/releases/el96-y2@el102-lrel@lvms.shtest/scenarios-bootc/el10/releases/el96-y2@el102-lrel@standard1.shtest/scenarios-bootc/el10/releases/el96-y2@el102-lrel@standard2.shtest/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@lvms.shtest/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard1.shtest/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard2.sh
💤 Files with no reviewable changes (2)
- test/scenarios-bootc/el10/releases/el102-lrel@standard2.sh
- test/scenarios-bootc/el10/releases/el102-lrel@standard1.sh
✅ Files skipped from review due to trivial changes (12)
- test/image-blueprints-bootc/layer4-release/group2/rhel102-bootc-brew-lrel-fips.containerfile
- test/scenarios-bootc/el10/releases/el102-lrel@nightly-brew-standard1.sh
- test/scenarios-bootc/el10/releases/el102-lrel@iso-standard1.sh
- test/scenarios-bootc/el10/releases/el102-lrel@nightly-brew-standard2.sh
- test/scenarios-bootc/el10/releases/el102-lrel@configuration.sh
- test/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard1.sh
- test/scenarios-bootc/el10/releases/el102-lrel@osconfig-router.sh
- test/scenarios-bootc/el10/releases/el102-lrel@tlsv13-standard2.sh
- test/scenarios-bootc/el10/releases/el102-lrel@fips.sh
- test/scenarios-bootc/el10/releases/el102-lrel@ai-model-serving-online.sh
- test/scenarios-bootc/el10/releases/el102-lrel@dual-stack.sh
- test/scenarios-bootc/el10/releases/el102-lrel@published-images-standard1.sh
🚧 Files skipped from review as they are similar to previous changes (13)
- test/scenarios-bootc/el10/releases/el102-lrel@iso-standard2.sh
- test/scenarios-bootc/el10/releases/el102-lrel@multi-nic.sh
- test/scenarios-bootc/el10/releases/el96-y2@el102-lrel@lvms.sh
- test/scenarios-bootc/el10/releases/el96-y2@el102-lrel@standard2.sh
- test/scenarios-bootc/el10/releases/el102-lrel@tlsv13-standard1.sh
- test/scenarios-bootc/el10/releases/el96-y2@el102-lrel@standard1.sh
- test/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@standard2.sh
- test/scenarios-bootc/el10/releases/el96-y1@el102-lrel@lvms.sh
- test/scenarios-bootc/el10/releases/el102-lrel@low-latency.sh
- test/scenarios-bootc/el10/releases/el102-lrel@published-images-standard2.sh
- test/scenarios-bootc/el10/releases/el102-lrel@multi-config-standard1.sh
- test/scenarios-bootc/el10/releases/el96-y1@el102-lrel@standard1.sh
- test/scenarios-bootc/el10/releases/el98-lrel@el102-lrel@lvms.sh
Contributor
Author
|
/test e2e-aws-tests-bootc-release-el10 |
1 similar comment
Contributor
|
/test e2e-aws-tests-bootc-release-el10 |
Contributor
|
/test e2e-aws-tests-bootc-release-arm-el10 |
agullon
reviewed
Apr 8, 2026
| exit_if_image_not_set "${LATEST_RELEASE_IMAGE_URL}" | ||
|
|
||
| run_tests host1 \ | ||
| --variable "EXPECTED_OS_VERSION:10.2" \ |
Contributor
There was a problem hiding this comment.
the RF test that checks the OS versions fails because afaik ART is unable to build the bootc image based on RHEL 10. Not a blocker for this PR.
Contributor
Author
There was a problem hiding this comment.
I've disabled the scenario for now, and I created a bug to reenable it.
Contributor
Author
|
/test ? |
Contributor
Author
|
/test e2e-aws-tests-cache |
1 similar comment
Contributor
Author
|
/test e2e-aws-tests-cache |
Contributor
|
/test e2e-aws-tests-cache-arm |
Contributor
|
/test e2e-aws-tests-cache |
Contributor
|
/override ci/prow/e2e-aws-tests-cache-arm |
Contributor
|
/verified by @agullon |
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. |
Contributor
|
@agullon: Overrode contexts on behalf of agullon: ci/prow/e2e-aws-tests-bootc-el10, ci/prow/e2e-aws-tests-cache, ci/prow/e2e-aws-tests-cache-arm 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. |
Contributor
|
/lgtm |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: agullon, vanhalenar 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 |
openshift-ci
bot
added
the
approved
Contributor
|
/override ci/prow/e2e-aws-tests-bootc-arm-el10 |
Contributor
|
@agullon: Overrode contexts on behalf of agullon: ci/prow/e2e-aws-tests-bootc-arm-el10, ci/prow/e2e-aws-tests-bootc-arm-el9, ci/prow/e2e-aws-tests-bootc-el9 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. |
Contributor
|
@vanhalenar: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
Contributor
|
/override ci/prow/e2e-aws-tests |
Contributor
|
@agullon: Overrode contexts on behalf of agullon: ci/prow/e2e-aws-tests 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.