OPCT-420: Add OPCT conformance upgrade periodic jobs for platform-external on AWS by redhat-chai-bot · Pull Request #79992 · openshift/release

redhat-chai-bot · 2026-06-02T17:17:26Z

What

Add opct-platform-external-aws-upgrade periodic jobs to the upgrade-from-stable configs for OCP 4.19, 4.20, 4.21, and 4.22.

Why

OPCT currently has upgrade conformance periodic jobs only on vSphere. There are no upgrade jobs exercising the OPCT upgrade workflow on AWS, which is needed to:

Compare release stability across different OCP versions on AWS
Provide baseline AWS upgrade results for partner validation
Detect etcd and other upgrade-related regressions on AWS platform-external installations

Related Jira: OPCT-400 (Stabilize OPCT validation workflows on OCP)

How

Adds a new test entry to each of the four upgrade config files:

openshift-release-main__nightly-4.19-upgrade-from-stable-4.18.yaml
openshift-release-main__nightly-4.20-upgrade-from-stable-4.19.yaml
openshift-release-main__nightly-4.21-upgrade-from-stable-4.20.yaml
openshift-release-main__nightly-4.22-upgrade-from-stable-4.21.yaml

The new job:

Uses the existing opct-conformance-external-aws workflow
Sets OPCT_RUN_MODE=upgrade and UPGRADE_TO_CHANNEL_TYPE=candidate
Runs @weekly with cluster_profile: openshift-org-aws
Does NOT enable CCM (PLATFORM_EXTERNAL_CCM_ENABLED is not set)
Reports failures to #forum-opct-updates
Follows the 4.Y-1 → 4.Y upgrade methodology from the openshift/release upgrade configs

The prowjob YAML was regenerated using make jobs.

Generated job names

periodic-ci-openshift-release-main-nightly-4.19-upgrade-from-stable-4.18-opct-platform-external-aws-upgrade
periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-opct-platform-external-aws-upgrade
periodic-ci-openshift-release-main-nightly-4.21-upgrade-from-stable-4.20-opct-platform-external-aws-upgrade
periodic-ci-openshift-release-main-nightly-4.22-upgrade-from-stable-4.21-opct-platform-external-aws-upgrade

Reference configs

Existing non-upgrade OPCT AWS job: opct-external-aws-ccm in nightly configs
Existing vSphere OPCT upgrade job: platform-external-vsphere-upgrade in OPCT repo configs

/cc @mtulio

openshift-ci · 2026-06-02T17:17:50Z

Hi @redhat-chai-bot. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

coderabbitai · 2026-06-02T17:17:55Z

Walkthrough

This PR adds the same opct-platform-external-aws-upgrade test job to four OpenShift release stream nightly configurations (4.19, 4.20, 4.21, and 4.22). Each test is scheduled via cron, reports failures and errors to #forum-opct-updates, runs on the AWS cluster profile in upgrade mode targeting the candidate channel, executes opct-conformance-external-aws, and has a 6-hour timeout.

Changes

OPCT External AWS Upgrade Tests

Layer / File(s)	Summary
OPCT upgrade test job configurations `ci-operator/config/openshift/release/openshift-release-main__nightly-4.19-upgrade-from-stable-4.18.yaml`, `ci-operator/config/openshift/release/openshift-release-main__nightly-4.20-upgrade-from-stable-4.19.yaml`, `ci-operator/config/openshift/release/openshift-release-main__nightly-4.21-upgrade-from-stable-4.20.yaml`, `ci-operator/config/openshift/release/openshift-release-main__nightly-4.22-upgrade-from-stable-4.21.yaml`	Adds identical `opct-platform-external-aws-upgrade` test entries to each release config: cron schedule, `reporter_config` to `#forum-opct-updates` for `failure`/`error`, `cluster_profile: openshift-org-aws`, `OPCT_RUN_MODE: upgrade`, `UPGRADE_TO_CHANNEL_TYPE: candidate`, `opct-conformance-external-aws` workflow, and `timeout: 6h0m0s`.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested labels

area/pipelines, rehearsals-ack

Suggested reviewers

sdminonne

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding OPCT conformance upgrade periodic jobs for platform-external on AWS across multiple OCP versions.
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 modifies only CI config YAML files, not Ginkgo test code. Custom check applies to Ginkgo test definitions, which are absent.
Test Structure And Quality	✅ Passed	This PR modifies only YAML CI-operator configuration files (not Ginkgo test code), so the custom check for Ginkgo test quality is not applicable.
Microshift Test Compatibility	✅ Passed	PR adds CI job definitions to YAML config files only; no new Ginkgo e2e tests are added. The check is not applicable to CI configuration changes.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR adds CI job configurations (YAML only), not Ginkgo e2e test code. The check applies only to new test code additions, which this PR does not contain.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies CI configuration files only (ci-operator/config/), not deployment manifests, operator code, or controllers. No scheduling constraints or topology-dependent code added.
Ote Binary Stdout Contract	✅ Passed	PR modifies only CI operator YAML config files, not test binary source code. OTE stdout contract applies to executable test code, not configurations.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR adds only CI job configuration (YAML) for existing OPCT workflow; no new Ginkgo e2e test code (It(), Describe(), etc.) is added, so check does not apply.
No-Weak-Crypto	✅ Passed	PR adds YAML CI job configurations with no weak cryptography, custom crypto implementations, or insecure comparisons detected.
Container-Privileges	✅ Passed	PR adds CI test job definitions without introducing any privileged containers, elevated capabilities, host access, or security escalations.
No-Sensitive-Data-In-Logs	✅ Passed	PR adds OPCT upgrade jobs with non-sensitive configuration; no passwords, tokens, API keys, PII, session IDs, internal hostnames, or customer data exposed in logging.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 and usage tips.}

mtulio · 2026-06-02T17:20:02Z

/assign @mtulio
/hold
/ok-to-test

openshift-ci-robot · 2026-06-02T17:21:38Z

@redhat-chai-bot: This pull request references OPCT-420 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

What

Add opct-platform-external-aws-upgrade periodic jobs to the upgrade-from-stable configs for OCP 4.19, 4.20, and 4.21.

Why

OPCT currently has upgrade conformance periodic jobs only on vSphere. There are no upgrade jobs exercising the OPCT upgrade workflow on AWS, which is needed to:

Compare release stability across different OCP versions on AWS

Provide baseline AWS upgrade results for partner validation

Detect etcd and other upgrade-related regressions on AWS platform-external installations

Related Jira: OPCT-400 (Stabilize OPCT validation workflows on OCP)

How

Adds a new test entry to each of the three upgrade config files:

openshift-release-main__nightly-4.19-upgrade-from-stable-4.18.yaml

openshift-release-main__nightly-4.20-upgrade-from-stable-4.19.yaml

openshift-release-main__nightly-4.21-upgrade-from-stable-4.20.yaml

The new job:

Uses the existing opct-conformance-external-aws workflow

Sets OPCT_RUN_MODE=upgrade and UPGRADE_TO_CHANNEL_TYPE=candidate

Runs @weekly with cluster_profile: openshift-org-aws

Does NOT enable CCM (PLATFORM_EXTERNAL_CCM_ENABLED is not set)

Reports failures to #forum-opct-updates

Follows the 4.Y-1 → 4.Y upgrade methodology from the openshift/release upgrade configs

The prowjob YAML was regenerated using make jobs.

Generated job names

periodic-ci-openshift-release-main-nightly-4.19-upgrade-from-stable-4.18-opct-platform-external-aws-upgrade

periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-opct-platform-external-aws-upgrade

periodic-ci-openshift-release-main-nightly-4.21-upgrade-from-stable-4.20-opct-platform-external-aws-upgrade

Reference configs

Existing non-upgrade OPCT AWS job: opct-external-aws-ccm in nightly configs

Existing vSphere OPCT upgrade job: platform-external-vsphere-upgrade in OPCT repo configs

/cc @mtulio

Summary by CodeRabbit

This PR extends OpenShift's CI infrastructure to include OPCT (OpenShift Platform Conformance Test) upgrade validation workflows on AWS. Three new periodic test jobs are added to the upgrade-from-stable CI configurations for OCP versions 4.19, 4.20, and 4.21.

The new jobs (opct-platform-external-aws-upgrade) run weekly and test the upgrade path from the previous stable version to the current version (4.18→4.19, 4.19→4.20, 4.20→4.21). Each job leverages the existing opct-conformance-external-aws workflow, configured with:

Upgrade mode enabled (OPCT_RUN_MODE=upgrade)

Target set to the candidate release channel (UPGRADE_TO_CHANNEL_TYPE=candidate)

AWS cluster profile without Cloud Credential Manager (openshift-org-aws)

6-hour timeout for completion

Results reported to the #forum-opct-updates Slack channel

This provides baseline conformance test coverage during platform upgrades on AWS, helping the team detect upgrade-related regressions and validate release stability across OpenShift versions on AWS platform-external installations.

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 openshift-eng/jira-lifecycle-plugin repository.

coderabbitai

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/config/openshift/release/openshift-release-main__nightly-4.19-upgrade-from-stable-4.18.yaml`:
- Around line 167-182: This job declares OPCT_RUN_MODE=upgrade and
UPGRADE_TO_CHANNEL_TYPE=candidate but reviewers noted you must ensure the
composed workflow opct-conformance-external-aws -> opct-conformance-test runs
the expected pre/setup and upgrade flow and that CCM is explicitly disabled;
verify opct-pre (opct-pre-setup-commands.sh) consumes OPCT_RUN_MODE and builds
upgrade_to_channel from UPGRADE_TO_CHANNEL_TYPE, ensure
opct-conformance-test-run-commands.sh uses OPCT_RUN_MODE to switch to
--mode=upgrade and the computed TARGET_RELEASE_IMAGE, and add or confirm
PLATFORM_EXTERNAL_CCM_ENABLED: "no" in the job env to match the CCM intent (and
update any commit/description that says “with CCM” to reflect CCM is disabled).

🪄 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: Enterprise

Run ID: 3b378929-86b1-42a4-a112-ca4b28694de4

📥 Commits

Reviewing files that changed from the base of the PR and between 68a0c59 and c8def77.

⛔ Files ignored due to path filters (1)

ci-operator/jobs/openshift/release/openshift-release-main-periodics.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (3)

ci-operator/config/openshift/release/openshift-release-main__nightly-4.19-upgrade-from-stable-4.18.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.20-upgrade-from-stable-4.19.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.21-upgrade-from-stable-4.20.yaml

mtulio · 2026-06-02T17:30:00Z

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.21-upgrade-from-stable-4.20-opct-platform-external-aws-upgrade

openshift-merge-bot · 2026-06-02T17:30:03Z

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

Add opct-platform-external-aws-ccm-upgrade periodic job to the upgrade-from-stable configs for OCP 4.19, 4.20, and 4.21. These jobs exercise the OPCT upgrade conformance workflow on platform-external installations on AWS (with CCM), using the existing opct-conformance-external-aws workflow with OPCT_RUN_MODE set to upgrade. This provides baseline upgrade stability results on AWS that can be compared with the existing vSphere upgrade jobs. The upgrade path follows the openshift/release convention of upgrading from 4.Y-1 to 4.Y (initial -> latest), as defined in each upgrade-from-stable variant file.

openshift-merge-bot · 2026-06-02T17:56:27Z

[REHEARSALNOTIFIER]
@redhat-chai-bot: 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
periodic-ci-openshift-release-main-nightly-4.19-upgrade-from-stable-4.18-opct-platform-external-aws-upgrade	N/A	periodic	Periodic changed
periodic-ci-openshift-release-main-nightly-4.21-upgrade-from-stable-4.20-opct-platform-external-aws-upgrade	N/A	periodic	Periodic changed
periodic-ci-openshift-release-main-nightly-4.22-upgrade-from-stable-4.21-opct-platform-external-aws-upgrade	N/A	periodic	Periodic changed
periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-opct-platform-external-aws-upgrade	N/A	periodic	Periodic 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.

mtulio · 2026-06-02T18:18:53Z

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.21-upgrade-from-stable-4.20-opct-platform-external-aws-upgrade
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-upgrade-from-stable-4.21-opct-platform-external-aws-upgrade

openshift-merge-bot · 2026-06-02T18:18:56Z

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

openshift-merge-bot · 2026-06-02T18:22:11Z

@mtulio: requesting more than one rehearsal in one comment is not supported. If you would like to rehearse multiple specific jobs, please separate the job names by a space in a single command.

mtulio · 2026-06-02T19:18:45Z

/lgtm

I will wait for the rehearsal job results to check if upgrade workflow will behave as expected.

/hold

mtulio · 2026-06-02T23:18:01Z

I got final results at job, overall it executed the job as expected and produced the report, the problem that the target version is not yet healthy due known bug affecting 4.21+, running older test versions for final review:

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.19-upgrade-from-stable-4.18-opct-platform-external-aws-upgrade periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-opct-platform-external-aws-upgrade

openshift-merge-bot · 2026-06-02T23:18:03Z

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

mtulio · 2026-06-03T01:23:27Z

Install failure, unrelated:
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.19-upgrade-from-stable-4.18-opct-platform-external-aws-
upgrade

openshift-merge-bot · 2026-06-03T01:23:29Z

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

openshift-merge-bot · 2026-06-03T01:26:43Z

@mtulio: job(s): periodic-ci-openshift-release-main-nightly-4.19-upgrade-from-stable-4.18-opct-platform-external-aws- either don't exist or were not found to be affected, and cannot be rehearsed

mtulio · 2026-06-03T01:35:13Z

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.19-upgrade-from-stable-4.18-opct-platform-external-aws-upgrade

openshift-merge-bot · 2026-06-03T01:35:16Z

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

mtulio · 2026-06-03T05:24:11Z

/hold cancel
/pj-rehearse ack

openshift-merge-bot · 2026-06-03T05:24:13Z

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

neisw · 2026-06-03T14:55:56Z

@mtulio any reason not to get 5.0 as well?

mtulio · 2026-06-03T16:17:53Z

@mtulio any reason not to get 5.0 as well?

@neisw it will be in follow up PRs for those reasons:

VCSP validations used to work in 2 or 3 Y versions prior current GA (4.22), so no one will take advantages now of having those artifacts, and for platform external we do have jobs (4.22+) covering that install that variant (platform type and provider)
There are known issues in the test framework affecting 4.21+ that won't take advantage of the 5.0 now, this would resolve old issue of having alternative of vsphere to cover unstable workflows (running currently only in vsphere) that we are observing alert channel

mtulio · 2026-06-03T16:18:06Z

/assign @neisw

neisw · 2026-06-03T16:47:21Z

/approve

openshift-ci · 2026-06-03T16:48:15Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mtulio, 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:

~~ci-operator/config/openshift/release/OWNERS~~ [neisw]
~~ci-operator/jobs/openshift/release/OWNERS~~ [neisw]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci · 2026-06-03T16:58:25Z

@redhat-chai-bot: 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-openshift-release-main-nightly-4.19-upgrade-from-stable-4.18-opct-platform-external-aws-upgrade	`50e77bb`	link	unknown	`/pj-rehearse periodic-ci-openshift-release-main-nightly-4.19-upgrade-from-stable-4.18-opct-platform-external-aws-upgrade`

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.

…penshift#79992) Add opct-platform-external-aws-ccm-upgrade periodic job to the upgrade-from-stable configs for OCP 4.19, 4.20, and 4.21. These jobs exercise the OPCT upgrade conformance workflow on platform-external installations on AWS (with CCM), using the existing opct-conformance-external-aws workflow with OPCT_RUN_MODE set to upgrade. This provides baseline upgrade stability results on AWS that can be compared with the existing vSphere upgrade jobs. The upgrade path follows the openshift/release convention of upgrading from 4.Y-1 to 4.Y (initial -> latest), as defined in each upgrade-from-stable variant file. Co-authored-by: Chai Bot <chai-bot@redhat.com>

openshift-ci Bot requested a review from mtulio June 2, 2026 17:17

openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jun 2, 2026

openshift-ci Bot assigned mtulio Jun 2, 2026

redhat-chai-bot changed the title ~~Add OPCT conformance upgrade periodic jobs on AWS platform-external~~ OPCT-420: Add OPCT conformance upgrade periodic jobs for platform-external on AWS Jun 2, 2026

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 2, 2026

coderabbitai Bot reviewed Jun 2, 2026

View reviewed changes

Comment thread .../config/openshift/release/openshift-release-main__nightly-4.19-upgrade-from-stable-4.18.yaml

redhat-chai-bot force-pushed the 06021708-bot-changes branch from c8def77 to 6d45532 Compare June 2, 2026 17:30

redhat-chai-bot force-pushed the 06021708-bot-changes branch from 6d45532 to 50e77bb Compare June 2, 2026 17:52

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

openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 3, 2026

openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jun 3, 2026

openshift-ci Bot assigned neisw Jun 3, 2026

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

openshift-merge-bot Bot merged commit 7d9a317 into openshift:main Jun 3, 2026
18 of 19 checks passed

Conversation

redhat-chai-bot commented Jun 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Why

How

Generated job names

Reference configs

Uh oh!

openshift-ci Bot commented Jun 2, 2026

Uh oh!

coderabbitai Bot commented Jun 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Suggested labels

Suggested reviewers

Uh oh!

mtulio commented Jun 2, 2026

Uh oh!

openshift-ci-robot commented Jun 2, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Why

How

Generated job names

Reference configs

Summary by CodeRabbit

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

mtulio commented Jun 2, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 2, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 2, 2026

Uh oh!

mtulio commented Jun 2, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 2, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 2, 2026

Uh oh!

mtulio commented Jun 2, 2026

Uh oh!

mtulio commented Jun 2, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 2, 2026

Uh oh!

mtulio commented Jun 3, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 3, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 3, 2026

Uh oh!

mtulio commented Jun 3, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 3, 2026

Uh oh!

mtulio commented Jun 3, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 3, 2026

Uh oh!

neisw commented Jun 3, 2026

Uh oh!

mtulio commented Jun 3, 2026

Uh oh!

mtulio commented Jun 3, 2026

Uh oh!

neisw commented Jun 3, 2026

Uh oh!

openshift-ci Bot commented Jun 3, 2026

Uh oh!

openshift-ci Bot commented Jun 3, 2026

Uh oh!

Uh oh!

Reviewers

redhat-chai-bot commented Jun 2, 2026 •

edited

Loading

coderabbitai Bot commented Jun 2, 2026 •

edited

Loading

openshift-ci-robot commented Jun 2, 2026 •

edited by atlassian Bot

Loading