Skip to content

amd-ci: update build_root to rhel-9, remove unused config - #82276

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
TomerNewman:amd-ci-update-build-root
Jul 23, 2026
Merged

amd-ci: update build_root to rhel-9, remove unused config#82276
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
TomerNewman:amd-ci-update-build-root

Conversation

@TomerNewman

@TomerNewman TomerNewman commented Jul 22, 2026

Copy link
Copy Markdown
Contributor
  • Update build_root from rhel-8-release-golang-1.18-openshift-4.12 to rhel-9-release-golang-1.24-openshift-4.22 across all 10 config files
  • Remove unused releases blocks from 9 variant configs (no workflow step references RELEASE_IMAGE_LATEST; clusters are provisioned via kcli using OCP_CLUSTER_VERSION env var)
  • Remove redundant SKIP_CLUSTER_DELETE env var that restates the step default of "false"

/cc @NataliShemtov

Summary by CodeRabbit

Updates rh-ecosystem-edge AMD CI configuration in ci-operator/config/rh-ecosystem-edge/amd-ci across 10 YAML variants to bump the build_root image stream tag from the RHEL 8 / OpenShift 4.12 / Go 1.18 release (rhel-8-release-golang-1.18-openshift-4.12) to the RHEL 9 / OpenShift 4.22 / Go 1.24 release (rhel-9-release-golang-1.24-openshift-4.22). It also removes the now-unused releases.latest.prerelease version bounds blocks from 9 of the variant files, and simplifies the AMD GPU e2e test step configuration by removing the redundant SKIP_CLUSTER_DELETE: "false" environment variable (and the corresponding steps.cluster_profile: aws-edge-infra where present).

TomerNewman requested rehearsal of the pull-ci-rh-ecosystem-edge...e2e-amd-ci-1-5-x job three times.

@openshift-ci
openshift-ci Bot requested a review from NataliShemtov July 22, 2026 09:18
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 22, 2026
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

AMD CI release YAMLs now use the RHEL 9, Go 1.24, OpenShift 4.22 build image. Prerelease version bounds and explicit AMD GPU E2E cluster cleanup/profile settings are removed across the configured release streams.

Changes

AMD CI release configuration

Layer / File(s) Summary
Build images and release constraints
ci-operator/config/rh-ecosystem-edge/amd-ci/*
Build manifests use the newer image stream tag and no longer define prerelease version bounds.
AMD GPU E2E step settings
ci-operator/config/rh-ecosystem-edge/amd-ci/*
The two AMD E2E variants remove SKIP_CLUSTER_DELETE and cluster_profile, while retaining workflows and remaining environment values.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

Suggested reviewers: natalishemtov, aopincar

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
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 edits ci-operator YAML job configs; no Ginkgo It/Describe/Context/When titles were added or modified.
Test Structure And Quality ✅ Passed PASS: PR only edits ci-operator YAML configs; no Go/Ginkgo test code or new It/Eventually/cleanup patterns to review.
Microshift Test Compatibility ✅ Passed Config-only PR: no Go/Ginkgo tests were added or changed, so MicroShift compatibility issues are not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed Only ci-operator/job YAML changed; no new or modified Ginkgo e2e tests were added, so the SNO check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed Only ci-operator/job YAML changed; no deployment/operator/controller scheduling manifests or topology/affinity/nodeSelector logic appeared in the diff.
Ote Binary Stdout Contract ✅ Passed PR only changes ci-operator YAML/job metadata; no process-level binary code or stdout logging paths were touched.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only updates CI YAML/presubmit wiring; no new Ginkgo tests or IPv4/external-network logic was added.
No-Weak-Crypto ✅ Passed Only CI YAML changed; the patch contains no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret/token comparisons.
Container-Privileges ✅ Passed No privileged or securityContext flags were added in the changed manifests; the diff only removes cloud labels/secret mounts and updates image tags.
No-Sensitive-Data-In-Logs ✅ Passed The PR only updates/removes CI YAML; the job file is deletions-only (0 insertions), and no log-related or secret-bearing additions appear in the diffs.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the main change: switching amd-ci build_root to RHEL 9 and cleaning up unused CI config.
✨ 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.

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

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-rh-ecosystem-edge-amd-ci-main-4.20-stable-e2e-amd-ci-1-5-x

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@TomerNewman
TomerNewman force-pushed the amd-ci-update-build-root branch from 02cc60d to 6972e07 Compare July 22, 2026 15:43
@TomerNewman

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-rh-ecosystem-edge-amd-ci-main-4.20-stable-e2e-amd-ci-1-5-x

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@TomerNewman: 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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.17-stable.yaml (1)

25-30: 🚀 Performance & Scalability | 🟠 Major | ⚡ Quick win

Restore cluster_profile on these AMD E2E jobs. ci-operator/platform-balance/step-jobs-by-platform.py only classifies tests that have steps.cluster_profile, so these entries are dropped from platform balancing without it:

  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.17-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.18-stable.yaml
🤖 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/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.17-stable.yaml`
around lines 25 - 30, Restore the missing cluster_profile field for all AMD E2E
job entries so platform balancing can classify them: update
ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.17-stable.yaml
at lines 25-30 and 32-41, and
ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.18-stable.yaml
at lines 25-41. Add the field under each job’s steps configuration while
preserving the existing AMD driver, GPU Operator, cluster, PCI device, and
workflow settings.
🤖 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.

Outside diff comments:
In
`@ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.17-stable.yaml`:
- Around line 25-30: Restore the missing cluster_profile field for all AMD E2E
job entries so platform balancing can classify them: update
ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.17-stable.yaml
at lines 25-30 and 32-41, and
ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.18-stable.yaml
at lines 25-41. Add the field under each job’s steps configuration while
preserving the existing AMD driver, GPU Operator, cluster, PCI device, and
workflow settings.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: a6774001-7698-4103-926e-80eaaa8c2bde

📥 Commits

Reviewing files that changed from the base of the PR and between 02cc60d and 6972e07.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (10)
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.16-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.17-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.18-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.19-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.20-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.21-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.22-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.23-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__5.0-stable.yaml
🚧 Files skipped from review as they are similar to previous changes (8)
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.21-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.19-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__5.0-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.22-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.23-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.16-stable.yaml
  • ci-operator/config/rh-ecosystem-edge/amd-ci/rh-ecosystem-edge-amd-ci-main__4.20-stable.yaml

@TomerNewman

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-rh-ecosystem-edge-amd-ci-main-4.20-stable-e2e-amd-ci-1-5-x

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 22, 2026
@TomerNewman
TomerNewman force-pushed the amd-ci-update-build-root branch from 6972e07 to 281853d Compare July 22, 2026 18:42
@openshift-ci openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 22, 2026
@TomerNewman TomerNewman changed the title [WIP] amd-ci: update build_root to rhel-9, remove unused config amd-ci: update build_root to rhel-9, remove unused config Jul 22, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 22, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@TomerNewman: 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-rh-ecosystem-edge-amd-ci-main-4.16-stable-e2e-amd-ci-1-4-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.16-stable-e2e-amd-ci-1-5-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.17-stable-e2e-amd-ci-1-4-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.17-stable-e2e-amd-ci-1-5-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.18-stable-e2e-amd-ci-1-4-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.18-stable-e2e-amd-ci-1-5-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.19-stable-e2e-amd-ci-1-4-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.19-stable-e2e-amd-ci-1-5-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.20-stable-e2e-amd-ci-1-4-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.20-stable-e2e-amd-ci-1-5-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.21-stable-e2e-amd-ci-1-4-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.21-stable-e2e-amd-ci-1-5-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.22-stable-e2e-amd-ci-1-4-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.22-stable-e2e-amd-ci-1-5-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.23-stable-e2e-amd-ci-1-4-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.23-stable-e2e-amd-ci-1-5-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-5.0-stable-e2e-amd-ci-1-4-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-5.0-stable-e2e-amd-ci-1-5-x rh-ecosystem-edge/amd-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.16-stable-images rh-ecosystem-edge/amd-ci presubmit Ci-operator config changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.17-stable-images rh-ecosystem-edge/amd-ci presubmit Ci-operator config changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.18-stable-images rh-ecosystem-edge/amd-ci presubmit Ci-operator config changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.19-stable-images rh-ecosystem-edge/amd-ci presubmit Ci-operator config changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.20-stable-images rh-ecosystem-edge/amd-ci presubmit Ci-operator config changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.21-stable-images rh-ecosystem-edge/amd-ci presubmit Ci-operator config changed
pull-ci-rh-ecosystem-edge-amd-ci-main-4.22-stable-images rh-ecosystem-edge/amd-ci presubmit Ci-operator config changed

A total of 29 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here

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.

@openshift-ci

openshift-ci Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

@TomerNewman: all tests passed!

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.

@TomerNewman

Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jul 23, 2026
@ggordaniRed

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 23, 2026
@openshift-ci

openshift-ci Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggordaniRed, TomerNewman

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-merge-bot
openshift-merge-bot Bot merged commit 21f6f2f into openshift:main Jul 23, 2026
16 checks passed
@TomerNewman
TomerNewman deleted the amd-ci-update-build-root branch July 23, 2026 09:04
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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants