Switch baremetal and end-to-end jobs to 4.22 by bshewale · Pull Request #4124 · openstack-k8s-operators/ci-framework

bshewale · 2026-08-20T07:38:24Z

This PR switched baremetal and end-to-end jobs to OCP- 4.22

Jobs:
baremetal and end-to-end

Signed-off-by: Bhagyashri Shewale bshewale@redhat.com

qodo-code-review · 2026-08-20T07:39:13Z

PR Summary by Qodo

Run baremetal and end-to-end CI jobs on OCP 4.22

⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Moves three EDPM baremetal jobs to OCP 4.22 CRC nodes.
• Moves the shared end-to-end base job and descendants to OCP 4.22.

Diagram

graph TD
  BM["Baremetal jobs"] --> NS6["4.22 6xlarge nodeset"] --> R6["CRC 2.62 runner"]
  E2E["E2E base job"] --> NS3["4.22 3xl nodeset"] --> R3["CRC 2.62 runner"]
  E2E --> CHILD["E2E child jobs"]

High-Level Assessment

Using the existing OCP 4.22 nodesets is the most direct and maintainable approach. It preserves each job family's current resource sizing and inheritance while avoiding duplicated nodeset definitions or unrelated parent-job changes.

Files changed (2) +4 / -4

Other (2) +4 / -4

edpm.yamlMove EDPM baremetal jobs to the OCP 4.22 nodeset +3/-3

Move EDPM baremetal jobs to the OCP 4.22 nodeset

• Switches the standard, bootc, and minor-update baremetal jobs from the CRC 2.56.0 6xlarge nodeset to the CRC 2.62.0 6xlarge nodeset for OCP 4.22 coverage.

zuul.d/edpm.yaml

end-to-end.yamlMove end-to-end jobs to the OCP 4.22 nodeset +1/-1

Move end-to-end jobs to the OCP 4.22 nodeset

• Updates the shared end-to-end base job from the CRC 2.56.0 3xl nodeset to CRC 2.62.0. Both inherited end-to-end job variants receive the new OCP 4.22 environment.

zuul.d/end-to-end.yaml

qodo-code-review · 2026-08-20T07:40:19Z

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1) 📜 Skill insights (0)

1. Modified zuul.d/edpm.yaml 📘 Rule violation ⚙ Maintainability

Description

This PR directly modifies the read-only/generated paths zuul.d/edpm.yaml and
zuul.d/end-to-end.yaml, which are prohibited by the compliance checklist. The nodeset changes
should instead be made through the supported generation or maintenance workflow, or another approved
mechanism.

Code

zuul.d/edpm.yaml[16]
+    nodeset: centos-9-crc-2-62-0-6xlarge

Evidence
The diff adds three new nodeset values directly in zuul.d/edpm.yaml and changes a nodeset directly
in zuul.d/end-to-end.yaml; the checklist prohibits any direct pull request modifications under
zuul.d/*.
AGENTS.md: Do Not Modify Read-Only/Generated or Local-Only Paths (zuul.d/*, custom/, hooks/playbooks/roles/)
zuul.d/edpm.yaml[16-16]
zuul.d/edpm.yaml[37-37]
zuul.d/edpm.yaml[54-54]
zuul.d/end-to-end.yaml[5-5]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The PR directly edits `zuul.d/edpm.yaml` and `zuul.d/end-to-end.yaml`, which the compliance checklist prohibits because `zuul.d/*` is a read-only/generated path.

## Issue Context
Apply the changed nodesets through the repository's supported source and regeneration or maintenance workflow, or otherwise obtain the approved mechanism for changing this configuration.

## Fix Focus Areas
- zuul.d/edpm.yaml[16-16]
- zuul.d/edpm.yaml[37-37]
- zuul.d/edpm.yaml[54-54]
- zuul.d/end-to-end.yaml[5-5]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Context sources

Review mode: 🚀 Fast: This is a small, localized CI configuration change that only updates nodeset versions and avoids security, API, schema, or complex logic risks.

Tip of the day

💡 Did you know, you can copy the agent prompt from any finding and feed it to your IDE agent

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

qodo-code-review · 2026-08-20T07:40:20Z

 - job:
    name: cifmw-crc-podified-edpm-baremetal
-    nodeset: centos-9-crc-2-56-0-6xlarge
+    nodeset: centos-9-crc-2-62-0-6xlarge


1. Modified zuul.d/edpm.yaml 📘 Rule violation ⚙ Maintainability

This PR directly modifies the read-only/generated paths zuul.d/edpm.yaml and zuul.d/end-to-end.yaml, which are prohibited by the compliance checklist. The nodeset changes should instead be made through the supported generation or maintenance workflow, or another approved mechanism.

Agent Prompt

## Issue description The PR directly edits `zuul.d/edpm.yaml` and `zuul.d/end-to-end.yaml`, which the compliance checklist prohibits because `zuul.d/*` is a read-only/generated path. ## Issue Context Apply the changed nodesets through the repository's supported source and regeneration or maintenance workflow, or otherwise obtain the approved mechanism for changing this configuration. ## Fix Focus Areas - zuul.d/edpm.yaml[16-16] - zuul.d/edpm.yaml[37-37] - zuul.d/edpm.yaml[54-54] - zuul.d/end-to-end.yaml[5-5]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

centosinfra-prod-github-app · 2026-08-20T10:07:45Z