Skip to content

Add 15 informing jobs to 4.23 nightly release controller - #83109

Open
redhat-chai-bot wants to merge 1 commit into
openshift:mainfrom
redhat-chai-bot:add-4.23-nightly-informing-jobs-v2
Open

Add 15 informing jobs to 4.23 nightly release controller#83109
redhat-chai-bot wants to merge 1 commit into
openshift:mainfrom
redhat-chai-bot:add-4.23-nightly-informing-jobs-v2

Conversation

@redhat-chai-bot

@redhat-chai-bot redhat-chai-bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Adds 15 informing jobs to the 4.23.0-0.nightly release controller config.

Changes

Appends 15 new verify entries to release-ocp-4.23.json (15 existing → 30 total).
Existing entries are untouched — the diff is pure additions with zero deletions.

New jobs

Metal upgrades + dualstack (5):

  • metal-ipi-ovn-upgrade — micro upgrade
  • metal-ipi-ovn-upgrade-minor — minor upgrade from 4.22
  • metal-ipi-upgrade-ovn-ipv6 — IPv6 micro upgrade
  • metal-ipi-upgrade-ovn-ipv6-minor — IPv6 minor upgrade from 4.22
  • metal-ipi-ovn-dualstack — dualstack e2e

vSphere upgrades (2):

  • vsphere-ovn-upgrade-micro — micro upgrade
  • vsphere-ovn-upgrade-minor — minor upgrade from 4.22

AWS SNO (3):

  • aws-ovn-single-node-upgrade-minor — minor upgrade from 4.22
  • aws-ovn-single-node-techpreview — TechPreview e2e
  • aws-ovn-single-node-techpreview-serial — TechPreview serial

CPMSO (3):

  • aws-control-plane-machine-set-operator
  • azure-control-plane-machine-set-operator
  • gcp-control-plane-machine-set-operator

GCP (1):

  • gcp-ovn-serial

Analysis (1):

  • upgrade-analysis-all — aggregate upgrade analysis (multiJobAnalysis: true, maxRetries: 2)

Configuration

All entries are optional: true with no maxRetries, matching 4.22 equivalents — except upgrade-analysis-all which uses maxRetries: 2 and multiJobAnalysis: true per the 4.22 pattern.

All periodic Prow jobs already exist. make release-controllers has been run to generate the companion priv/release-ocp-4.23.json.


AI-generated. Review for accuracy.

@neisw requested via Chai Bot

Summary by CodeRabbit

  • Adds 15 optional verification jobs to the OpenShift 4.23 nightly release controller.
  • Covers Metal, vSphere, AWS single-node, CPMSO on AWS/Azure/GCP, GCP serial testing, and aggregate upgrade analysis.
  • Uses nightly OpenShift 4.22 releases for minor-upgrade jobs.
  • Configures upgrade-analysis-all with maxRetries: 2 and multiJobAnalysis: true.
  • Regenerates the companion configuration with make release-controllers.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 7, 2026
@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

The release-controller configurations add optional OCP 4.23 verification jobs for AWS, Azure, GCP, metal, and vSphere. The changes include platform-specific upgrade, minor-upgrade, networking, single-node, and control-plane machine-set operator jobs.

Changes

OCP 4.23 verification jobs

Layer / File(s) Summary
Platform upgrade verification
core-services/release-controller/_releases/priv/release-ocp-4.23.json, core-services/release-controller/_releases/release-ocp-4.23.json
Added optional metal OVN, metal IPv6, vSphere OVN, and AWS single-node upgrade jobs. Minor-upgrade jobs use nightly 4.22 candidates.
Platform and networking scenarios
core-services/release-controller/_releases/priv/release-ocp-4.23.json, core-services/release-controller/_releases/release-ocp-4.23.json
Added AWS single-node tech-preview and serial jobs, GCP OVN serial jobs, and metal OVN dual-stack jobs.
Control-plane machine-set operators
core-services/release-controller/_releases/priv/release-ocp-4.23.json, core-services/release-controller/_releases/release-ocp-4.23.json
Added optional AWS, Azure, and GCP control-plane machine-set operator verification jobs.

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

Possibly related PRs

Suggested reviewers: deads2k, sosiouxme


Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Ote Binary Stdout Contract ❓ Inconclusive Placeholder Placeholder
✅ Passed checks (14 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the addition of 15 informing jobs to the 4.23 nightly release controller.
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 The PR changes only release-controller JSON entries and Prow job names; no Ginkgo test declarations or test titles were added or changed.
Test Structure And Quality ✅ Passed The patch changes only two release-controller JSON configuration files; it adds no Ginkgo test code, cluster operations, waits, or assertions to assess.
Microshift Test Compatibility ✅ Passed The pull request changes only two release-controller JSON configuration files and adds no Ginkgo e2e tests, so MicroShift test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The commit changes only two release-controller JSON files and adds Prow job configuration, not Ginkgo test source; therefore the SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The change modifies only two release-controller JSON files; additions reference optional Prow jobs and contain no manifests, operator code, controllers, or scheduling constraints.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The commit changes only two release-controller JSON files. Added lines contain job declarations, not Ginkgo tests, IPv4 assumptions, or external connectivity.
No-Weak-Crypto ✅ Passed The PR changes only two valid JSON release configurations; added lines contain no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, crypto code, or secret comparisons.
Container-Privileges ✅ Passed The commit changes only two release-controller JSON files; added entries contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed The commit adds only JSON release verification metadata; added fields contain no logging directives, log calls, tokens, credentials, PII, hostnames, or customer data.
✨ 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 requested review from deads2k and sosiouxme August 7, 2026 15:35
@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: redhat-chai-bot
Once this PR has been reviewed and has the lgtm label, please assign dgoodwin for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@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: 2

🤖 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 `@core-services/release-controller/_releases/priv/release-ocp-4.23.json`:
- Around line 213-220: Restore the missing comma after the preceding property
and before the metal-ipi-ovn-upgrade configuration entry so the JSON remains
valid and the release controller can parse it.

In `@core-services/release-controller/_releases/release-ocp-4.23.json`:
- Around line 142-263: Resolve the upgrade-analysis-all release gate by ensuring
its prowJob name references a checked-in Prow definition under ci-operator/jobs;
add the matching ProwJob configuration if that job is intended to remain
enabled, otherwise remove the entire upgrade-analysis-all entry.
🪄 Autofix

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: 2a6bf9b7-7d9c-42c4-89a7-9d05d8920e05

📥 Commits

Reviewing files that changed from the base of the PR and between bbd3c97 and 148189a.

📒 Files selected for processing (2)
  • core-services/release-controller/_releases/priv/release-ocp-4.23.json
  • core-services/release-controller/_releases/release-ocp-4.23.json

Comment on lines +142 to +263
"metal-ipi-ovn-upgrade": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ipi-ovn-upgrade"
},
"upgrade": true
},
"metal-ipi-ovn-upgrade-minor": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-upgrade-from-stable-4.22-e2e-metal-ipi-ovn-upgrade"
},
"upgrade": true,
"upgradeFromRelease": {
"candidate": {
"stream": "nightly",
"version": "4.22"
}
}
},
"metal-ipi-upgrade-ovn-ipv6": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ipi-upgrade-ovn-ipv6"
},
"upgrade": true
},
"metal-ipi-upgrade-ovn-ipv6-minor": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-upgrade-from-stable-4.22-e2e-metal-ipi-upgrade-ovn-ipv6"
},
"upgrade": true,
"upgradeFromRelease": {
"candidate": {
"stream": "nightly",
"version": "4.22"
}
}
},
"metal-ipi-ovn-dualstack": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ipi-ovn-dualstack"
}
},
"vsphere-ovn-upgrade-micro": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-ci-4.23-e2e-vsphere-ovn-upgrade"
},
"upgrade": true
},
"vsphere-ovn-upgrade-minor": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-ci-4.23-upgrade-from-stable-4.22-e2e-vsphere-ovn-upgrade"
},
"upgrade": true,
"upgradeFromRelease": {
"candidate": {
"stream": "nightly",
"version": "4.22"
}
}
},
"aws-ovn-single-node-upgrade-minor": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-upgrade-from-stable-4.22-e2e-aws-upgrade-ovn-single-node"
},
"upgrade": true,
"upgradeFromRelease": {
"candidate": {
"stream": "nightly",
"version": "4.22"
}
}
},
"aws-ovn-single-node-techpreview": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-e2e-aws-ovn-single-node-techpreview"
}
},
"aws-ovn-single-node-techpreview-serial": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-e2e-aws-ovn-single-node-techpreview-serial"
}
},
"aws-control-plane-machine-set-operator": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.23-periodics-e2e-aws"
}
},
"azure-control-plane-machine-set-operator": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.23-periodics-e2e-azure"
}
},
"gcp-control-plane-machine-set-operator": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.23-periodics-e2e-gcp"
}
},
"gcp-ovn-serial": {
"optional": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-e2e-gcp-ovn-serial"
}
},
"upgrade-analysis-all": {
"optional": true,
"maxRetries": 2,
"multiJobAnalysis": true,
"prowJob": {
"name": "periodic-ci-openshift-release-main-nightly-4.23-upgrade-analysis-all"
}

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

config='core-services/release-controller/_releases/release-ocp-4.23.json'
jq -e . "$config" >/dev/null

keys=(
  metal-ipi-ovn-upgrade
  metal-ipi-ovn-upgrade-minor
  metal-ipi-upgrade-ovn-ipv6
  metal-ipi-upgrade-ovn-ipv6-minor
  metal-ipi-ovn-dualstack
  vsphere-ovn-upgrade-micro
  vsphere-ovn-upgrade-minor
  aws-ovn-single-node-upgrade-minor
  aws-ovn-single-node-techpreview
  aws-ovn-single-node-techpreview-serial
  aws-control-plane-machine-set-operator
  azure-control-plane-machine-set-operator
  gcp-control-plane-machine-set-operator
  gcp-ovn-serial
  upgrade-analysis-all
)

missing=0
for key in "${keys[@]}"; do
  job="$(jq -er --arg key "$key" '.verify[$key].prowJob.name' "$config")"
  if ! rg -n -F --glob '*.yaml' --glob '*.yml' "name: $job" ci-operator/jobs; then
    printf 'Missing ProwJob definition: %s (%s)\n' "$key" "$job" >&2
    missing=1
  fi
done

exit "$missing"

Repository: openshift/release

Length of output: 5980


Resolve the upgrade-analysis-all ProwJob reference.

periodic-ci-openshift-release-main-nightly-4.23-upgrade-analysis-all is not present under ci-operator/jobs, so this enabled release gate can be launched without a checked-in Prow definition. Add the matching ProwJob config or remove the gate.

🤖 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 `@core-services/release-controller/_releases/release-ocp-4.23.json` around
lines 142 - 263, Resolve the upgrade-analysis-all release gate by ensuring its
prowJob name references a checked-in Prow definition under ci-operator/jobs; add
the matching ProwJob configuration if that job is intended to remain enabled,
otherwise remove the entire upgrade-analysis-all entry.

Source: Learnings

Adds metal upgrades (IPv4+IPv6 micro/minor + dualstack), vSphere upgrades
(micro/minor), AWS SNO (minor upgrade + techpreview), CPMSO (AWS/Azure/GCP),
and gcp-ovn-serial.

All new entries match 4.22 equivalents with no maxRetries.
@redhat-chai-bot
redhat-chai-bot force-pushed the add-4.23-nightly-informing-jobs-v2 branch from 148189a to fbec55d Compare August 7, 2026 16:14
@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@redhat-chai-bot: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

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.

@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 `@core-services/release-controller/_releases/release-ocp-4.23.json`:
- Around line 221-255: Reconcile the release objective with the configured
verification jobs: either add the missing upgrade-analysis-all release entry and
its corresponding 4.23 ProwJob, or revise the objective to accurately describe
the 14 jobs currently added. Keep the release gate and objective consistent.
🪄 Autofix

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: d1f44718-d799-45da-9c78-f06321c14eec

📥 Commits

Reviewing files that changed from the base of the PR and between 88ce08f and fbec55d.

📒 Files selected for processing (2)
  • core-services/release-controller/_releases/priv/release-ocp-4.23.json
  • core-services/release-controller/_releases/release-ocp-4.23.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • core-services/release-controller/_releases/priv/release-ocp-4.23.json

Comment thread core-services/release-controller/_releases/release-ocp-4.23.json
@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@redhat-chai-bot: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants