Skip to content

DNM: swap to rhel 8 for testing - #82644

Open
jbpratt wants to merge 2 commits into
openshift:mainfrom
jbpratt:patch-2
Open

DNM: swap to rhel 8 for testing#82644
jbpratt wants to merge 2 commits into
openshift:mainfrom
jbpratt:patch-2

Conversation

@jbpratt

@jbpratt jbpratt commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

Updates OpenShift CI’s Quay OMR v2 disconnected install testing to use official RHEL 8 hourly AWS AMIs for the dedicated host provisioning (including the AMI resolution failure message). It also adjusts the OMR v2 health-check command used during the install step to drop curl --retry-all-errors (not supported on RHEL 8 curl), while keeping the existing retry behavior.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 35737f00-3029-4cd2-9818-5365dfeb92a0

📥 Commits

Reviewing files that changed from the base of the PR and between a8b30b8 and a2fabe3.

📒 Files selected for processing (1)
  • ci-operator/step-registry/quay/omr-v2/install/quay-omr-v2-install-commands.sh

Walkthrough

OMR v2 provisioning now selects official RHEL 8 hourly AMIs and updates the health-check curl command for curl versions available on RHEL 8.

Changes

RHEL 8 compatibility

Layer / File(s) Summary
RHEL 8 AMI selection and diagnostics
ci-operator/step-registry/quay/omr-v2/host-provision/quay-omr-v2-host-provision-commands.sh
The AMI filter and failure message now target official RHEL 8 images.
Health-check curl compatibility
ci-operator/step-registry/quay/omr-v2/install/quay-omr-v2-install-commands.sh
The health check removes --retry-all-errors, retains retry settings, and documents the RHEL 8 curl version constraint.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: aroyoredhat, marcusk19

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: switching testing to RHEL 8.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed PR only changes two shell scripts; no Ginkgo tests or titles were added/modified, so no unstable test names are present.
Test Structure And Quality ✅ Passed PR only changes two CI shell scripts; no Ginkgo test code or test assertions/setup patterns were modified.
Microshift Test Compatibility ✅ Passed PASS: The PR only edits ci-operator shell step scripts (AMI and curl retry flags); no Ginkgo test additions or MicroShift-sensitive APIs/resources were introduced.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only changes ci-operator shell scripts; no new Ginkgo e2e tests or SNO-sensitive test logic were added.
Topology-Aware Scheduling Compatibility ✅ Passed The PR only changes CI shell scripts for AMI discovery and curl flags; no scheduling, replica, affinity, nodeSelector, or topology logic was added.
Ote Binary Stdout Contract ✅ Passed Only a shell-step curl flag/comment changed; no OTE binary process-level stdout writes were added.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No new Ginkgo e2e tests were added; the diff only changes shell step scripts, and the health check targets the local OMR host rather than public internet.
No-Weak-Crypto ✅ Passed Changed shell scripts only use sha256sum and openssl rand; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons found.
Container-Privileges ✅ Passed Changed step-registry scripts and related ref yamls contain no privileged/hostPID/hostNetwork/hostIPC/SYS_ADMIN/allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed Changed lines only alter AMI selection and a curl compatibility comment; no new secret/PII/internal-hostname logging was introduced.
✨ 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.

@jbpratt

jbpratt commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-quay-quay-master-omr-v2-upgrade-v3-disconnected-install

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@jbpratt: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/step-registry/quay/omr-v2/host-provision/quay-omr-v2-host-provision-commands.sh`:
- Line 105: Update the documentation in the host-provision step reference for
OMR_V2_AMI_ID and the provisioned host to state RHEL 8 instead of RHEL 9,
ensuring explicit AMI inputs and generated guidance match the RHEL 8 discovery
behavior.
🪄 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: Pro Plus

Run ID: 345f9648-bfcf-4c21-b89b-929a94396aa2

📥 Commits

Reviewing files that changed from the base of the PR and between 64e7ba1 and a8b30b8.

📒 Files selected for processing (1)
  • ci-operator/step-registry/quay/omr-v2/host-provision/quay-omr-v2-host-provision-commands.sh

--owners 309956199498 \
--filters \
'Name=name,Values=RHEL-9.*_HVM-*-x86_64-*-Hourly2-GP3' \
'Name=name,Values=RHEL-8.*_HVM-*-x86_64-*-Hourly2-GP3' \

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Update the step contract to RHEL 8.

The script now discovers RHEL 8 AMIs, but ci-operator/step-registry/quay/omr-v2/host-provision/quay-omr-v2-host-provision-ref.yaml still documents OMR_V2_AMI_ID and the provisioned host as RHEL 9. Update that file’s documentation to RHEL 8 so explicit AMI inputs and generated guidance match the new behavior.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/step-registry/quay/omr-v2/host-provision/quay-omr-v2-host-provision-commands.sh`
at line 105, Update the documentation in the host-provision step reference for
OMR_V2_AMI_ID and the provisioned host to state RHEL 8 instead of RHEL 9,
ensuring explicit AMI inputs and generated guidance match the RHEL 8 discovery
behavior.

@openshift-ci
openshift-ci Bot requested review from Marcusk19 and aroyoredhat July 29, 2026 20:33
@jbpratt

jbpratt commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

/label wip

@openshift-ci

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jbpratt

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 29, 2026
@openshift-ci

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

@jbpratt: The label(s) /label wip cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, rebase/manual, cluster-config-api-changed, run-integration-tests, verified, ready-for-human-review, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/skip-dependent-bug-check, jira/valid-bug, ok-to-test, priority/ci-critical, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label wip

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.

@harishsurf

Copy link
Copy Markdown
Contributor

/hold

@jbpratt

jbpratt commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

/label do-not-merge/work-in-progress

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 29, 2026
@openshift-ci

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

@jbpratt: The label(s) /label do-not-merge/work-in-progress cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, rebase/manual, cluster-config-api-changed, run-integration-tests, verified, ready-for-human-review, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/skip-dependent-bug-check, jira/valid-bug, ok-to-test, priority/ci-critical, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label do-not-merge/work-in-progress

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

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

@jbpratt: 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/rehearse/periodic-ci-quay-quay-master-omr-v2-upgrade-v3-disconnected-install a8b30b8 link unknown /pj-rehearse periodic-ci-quay-quay-master-omr-v2-upgrade-v3-disconnected-install

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.

Signed-off-by: Brady Pratt <bpratt@redhat.com>
@jbpratt

jbpratt commented Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-quay-quay-master-omr-v2-upgrade-v3-disconnected-install

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@jbpratt: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@jbpratt: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-quay-mirror-registry-main-omr-v2-disconnected-install quay/mirror-registry presubmit Registry content changed
periodic-ci-quay-quay-master-omr-v2-upgrade-v3-disconnected-install N/A periodic Registry content changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants