Skip to content

Add informing verification jobs for 4.23 ppc64le nightly stream - #83069

Merged
openshift-merge-bot[bot] merged 3 commits into
openshift:mainfrom
redhat-chai-bot:add-423-ppc64le-informing-jobs
Aug 6, 2026
Merged

Add informing verification jobs for 4.23 ppc64le nightly stream#83069
openshift-merge-bot[bot] merged 3 commits into
openshift:mainfrom
redhat-chai-bot:add-423-ppc64le-informing-jobs

Conversation

@redhat-chai-bot

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

Copy link
Copy Markdown
Contributor

Adds verification jobs to the 4.23.0-0.nightly-ppc64le release controller stream, modeled after the 5.0 ppc64le equivalents. Both jobs are configured as informing (optional: true) with maxRetries: 2.

Jobs added

  • e2e-ppc64leperiodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-ovn-remote-s2s-libvirt-ppc64le
  • install-analysis-allperiodic-ci-openshift-multiarch-main-nightly-4.23-install-analysis-all-ppc64le (multiJobAnalysis: true)

Changes

  1. core-services/release-controller/_releases/release-ocp-4.23-ppc64le.json — populated empty verify section with both informing jobs
  2. ci-operator/jobs/openshift/multiarch/openshift-multiarch-master-periodics.yaml — added ProwJob definition for install-analysis-all-ppc64le (copied from 5.0, version changed to 4.23)
  3. core-services/release-controller/_releases/priv/release-ocp-4.23-ppc64le.json — generated via make release-controllers

AI-generated. Review for accuracy.

@neisw requested via Chai Bot

Summary by CodeRabbit

Updates the OpenShift 4.23 ppc64le release controller configuration to add two optional verification jobs:

  • e2e-ppc64le
  • install-analysis-all, with multiJobAnalysis: true

Both jobs allow two retries. The regenerated release configuration includes the associated Prow job definitions and enables these checks in the 4.23.0-0.nightly-ppc64le release stream.

@coderabbitai

coderabbitai Bot commented Aug 6, 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: a9cf4f89-6060-44c0-a5b1-406dde55adc2

📥 Commits

Reviewing files that changed from the base of the PR and between 6200a4e and 1bb5095.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/multiarch/openshift-multiarch-master-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (2)
  • core-services/release-controller/_releases/priv/release-ocp-4.23-ppc64le.json
  • core-services/release-controller/_releases/release-ocp-4.23-ppc64le.json

Walkthrough

The release configurations now define optional e2e-ppc64le and install-analysis-all verification jobs. Both jobs allow two retries and reference Prow jobs. The install-analysis job enables multi-job analysis.

Changes

OCP 4.23 ppc64le verification

Layer / File(s) Summary
Configure ppc64le verification jobs
core-services/release-controller/_releases/priv/release-ocp-4.23-ppc64le.json, core-services/release-controller/_releases/release-ocp-4.23-ppc64le.json
Both release configurations replace empty verify objects with disabled optional e2e-ppc64le and install-analysis-all jobs. Each job allows two retries and references a Prow job. install-analysis-all enables multi-job analysis.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

🚥 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 and concisely describes the addition of informing verification jobs to the 4.23 ppc64le nightly stream.
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 adds release JSON and one Prow YAML job only; no Ginkgo It, Describe, Context, or When titles are added. The test alias is the static release-payload-install-analysis.
Test Structure And Quality ✅ Passed The aggregate PR changes only release JSON and Prow YAML; it contains no test files or Ginkgo constructs, so the Ginkgo test-quality criteria do not apply.
Microshift Test Compatibility ✅ Passed The PR changes release JSON and a Prow job definition only; it adds no Ginkgo e2e tests or test code, so MicroShift API compatibility checks do not apply.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The actual patch only adds generated release-controller JSON verification configuration; it adds no Ginkgo e2e tests or multi-node test logic, so SNO compatibility checks are not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The PR changes release JSON and one Prow periodic-job definition; the added job has no affinity, anti-affinity, spread, selector, toleration, replica, or PDB constraints.
Ote Binary Stdout Contract ✅ Passed The PR changes only two JSON release configs and one YAML ProwJob definition; no OTE binary or process-level suite code is modified, so the stdout contract is not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR adds only JSON release configuration and a YAML Prow job; the diff adds no Ginkgo test declarations or test source, so this check is not applicable.
No-Weak-Crypto ✅ Passed The PR changes only JSON/YAML release and ProwJob configuration; the added lines contain no weak algorithms, crypto implementations, or secret comparisons.
Container-Privileges ✅ Passed The PR adds a Prow Kubernetes job and release JSON only; added content contains no privileged:true, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation:true.
No-Sensitive-Data-In-Logs ✅ Passed The only added lines define verification metadata and Prow job names; they add no logging calls or passwords, tokens, API keys, PII, session IDs, 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 dgoodwin and rvanderp3 August 6, 2026 21:23
@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.

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

openshift-ci Bot commented Aug 6, 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.

@neisw

neisw commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, neisw, redhat-chai-bot

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 Aug 6, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 1c5acc9 into openshift:main Aug 6, 2026
13 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. 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.

3 participants