Skip to content

[release-4.17] USHIFT-7042: Enable EUS repos for RHEL 9.4 bootc test images#6734

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.17from
pacevedom:USHIFT-7042-4.17
May 26, 2026
Merged

[release-4.17] USHIFT-7042: Enable EUS repos for RHEL 9.4 bootc test images#6734
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.17from
pacevedom:USHIFT-7042-4.17

Conversation

@pacevedom
Copy link
Copy Markdown
Contributor

The rhel-bootc:9.4 base image ships with repos pointing to RHEL 9 latest content instead of RHEL 9.4 EUS. This causes dnf to install greenboot-rs (0.16.x) from RHEL 9.8 instead of bash greenboot (0.15.x) from 9.4 EUS. Greenboot-rs sets RefuseManualStartStop=yes on the greenboot-healthcheck.service unit, breaking both the test framework's Restart Greenboot keyword and the rollback/reboot mechanism.

Lock releasever and enable EUS repositories before installing packages, matching the pattern used on release-4.20+ via rpm-repo-config.sh.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 26, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 26, 2026

@pacevedom: This pull request references USHIFT-7042 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.18.z" instead.

Details

In response to this:

The rhel-bootc:9.4 base image ships with repos pointing to RHEL 9 latest content instead of RHEL 9.4 EUS. This causes dnf to install greenboot-rs (0.16.x) from RHEL 9.8 instead of bash greenboot (0.15.x) from 9.4 EUS. Greenboot-rs sets RefuseManualStartStop=yes on the greenboot-healthcheck.service unit, breaking both the test framework's Restart Greenboot keyword and the rollback/reboot mechanism.

Lock releasever and enable EUS repositories before installing packages, matching the pattern used on release-4.20+ via rpm-repo-config.sh.

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.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 26, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 385ae8cf-3520-4d98-aaa6-0fbc8eaab8fe

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from ggiguash and pmtk May 26, 2026 06:13
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 26, 2026
The rhel-bootc:9.4 base image ships with repos pointing to RHEL 9
latest content instead of RHEL 9.4 EUS. This causes dnf to install
greenboot-rs (0.16.x) from RHEL 9.8 instead of bash greenboot (0.15.x)
from 9.4 EUS. Greenboot-rs sets RefuseManualStartStop=yes on the
greenboot-healthcheck.service unit, breaking both the test framework's
Restart Greenboot keyword and the rollback/reboot mechanism.

Lock releasever and enable EUS repositories before installing packages,
matching the pattern used on release-4.20+ via rpm-repo-config.sh.
@kasturinarra
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 26, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 26, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kasturinarra, pacevedom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@pacevedom
Copy link
Copy Markdown
Contributor Author

/test metal-bootc-periodic-test-arm

@pacevedom
Copy link
Copy Markdown
Contributor Author

/label jira/valid-bug
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels May 26, 2026
@pacevedom
Copy link
Copy Markdown
Contributor Author

/override ci/prow/ocp-full-conformance-rhel-eus

Unrelated failure, doesnt use the changes included in this PR.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 26, 2026

@pacevedom: Overrode contexts on behalf of pacevedom: ci/prow/ocp-full-conformance-rhel-eus

Details

In response to this:

/override ci/prow/ocp-full-conformance-rhel-eus

Unrelated failure, doesnt use the changes included in this PR.

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 26, 2026

@pacevedom: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/ocp-full-conformance-rhel-eus 8e0245d link true /test ocp-full-conformance-rhel-eus

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@ggiguash
Copy link
Copy Markdown
Contributor

/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 26, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

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.

@openshift-merge-bot openshift-merge-bot Bot merged commit f72f7e9 into openshift:release-4.17 May 26, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants