[vr4manta]

SPLAT-2998

Changes

• Promote VSphereMultiVCenterDay2 to GA in OCP 4.22

[openshift-merge-bot]

Pipeline controller notification

This PR uses the pipeline controller for second-stage tests. Selection and triggering follow the repository configuration.

Use /test ? to list jobs and /pipeline help for commands.

[openshift-ci-robot]

@vr4manta: This pull request references SPLAT-2998 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 "4.22.0" version, but no target version was set.

Details

In response to this:

SPLAT-2998

Changes

• Promote VSphereMultiVCenterDay2 to GA in OCP 4.22

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.

[openshift-ci]

Hello @vr4manta! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository YAML (base), Central YAML (inherited)
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 8215a291-c3f2-48a1-8c53-008dfc525bf8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

_{Comment @coderabbitai help to get the list of available commands.}

[jcpowermac]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jcpowermac
Once this PR has been reviewed and has the lgtm label, please assign joelspeed 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:

• OWNERS

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]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test e2e-vsphere-ovn

[redhat-chai-bot]

/override-sticky ci/prow/e2e-aws-ovn-hypershift

Automated risk analysis: The observed failure is consistent with recurring HyperShift control-plane restart noise and is unrelated to the vSphere API changes in this PR.

Job classification: Eligible long-running AWS HyperShift e2e/upgrade integration job (hypershift-aws-run-e2e-external); the run lasted 42m31s.
Revision check: Run 00d3824528f14768cc1200171bc7727fe9193ec4; current PR HEAD 00d3824528f14768cc1200171bc7727fe9193ec4; match.
Execution status: Tests executed. TestUpgradeControlPlane/ValidateHostedCluster/EnsureNoCrashingPods failed after detecting leader-election failure in the manager container and restartCount=1 for etcd.
Completed supporting jobs: ci/prow/e2e-vsphere-ovn, ci/prow/e2e-aws-ovn, ci/prow/e2e-aws-ovn-techpreview, ci/prow/e2e-upgrade, ci/prow/verify-crd-schema, and ci/prow/verify-feature-promotion passed. Pending: tide.
Fleet-wide failure rate: The same presubmit job passed on 3/3 other PR runs in the last 30 days (100%, n=3; small sample). For the exact test, recent 7-day Sippy results report 97.6% overall, 98.2% on AWS, and 97.6% for HyperShift/external; the current 4.22 report shows 98.6% (139/141), versus 97.3% (146/150) in the previous window.
Open regressions: None found for this exact test in 4.22; Sippy reports open_bugs=0.
Linked bugs: No open linked bug is shown in the exact-test Sippy report (open_bugs=0).
Overlap assessment: The PR promotes VSphereMultiVCenterDay2 and updates vSphere-specific CRD validation and feature-gate data. The failed check is an AWS HyperShift control-plane upgrade test; no direct or indirect overlap with the changed vSphere surface was identified.
Missing-coverage risk: Low for the PR's vSphere change given the passing vSphere e2e and schema/feature-promotion checks. This override does not establish that the HyperShift upgrade path is healthy; it waives this unrelated failure for this PR.
Prior bot activity on this SHA: One /test e2e-aws-ovn-hypershift was issued at 19:37:50Z and produced this failed run; no prior override.
Decision and action: Override this failure as unrelated to the PR, based on the repeated test-level restart failure signal, current passing checks for the changed surface, and lack of overlap.

If you disagree with this assessment, rerun the job on the current revision with /test e2e-aws-ovn-hypershift.

---

AI-generated. Review for accuracy.

[openshift-ci]

@redhat-chai-bot: Overrode contexts on behalf of redhat-chai-bot: ci/prow/e2e-aws-ovn-hypershift

These overrides will persist across retests on the current HEAD SHA. Pushing a new commit will clear them. Use /override-cancel to remove them.

Details

In response to this:

/override-sticky ci/prow/e2e-aws-ovn-hypershift

Automated risk analysis: The observed failure is consistent with recurring HyperShift control-plane restart noise and is unrelated to the vSphere API changes in this PR.

Job classification: Eligible long-running AWS HyperShift e2e/upgrade integration job (hypershift-aws-run-e2e-external); the run lasted 42m31s.
Revision check: Run 00d3824528f14768cc1200171bc7727fe9193ec4; current PR HEAD 00d3824528f14768cc1200171bc7727fe9193ec4; match.
Execution status: Tests executed. TestUpgradeControlPlane/ValidateHostedCluster/EnsureNoCrashingPods failed after detecting leader-election failure in the manager container and restartCount=1 for etcd.
Completed supporting jobs: ci/prow/e2e-vsphere-ovn, ci/prow/e2e-aws-ovn, ci/prow/e2e-aws-ovn-techpreview, ci/prow/e2e-upgrade, ci/prow/verify-crd-schema, and ci/prow/verify-feature-promotion passed. Pending: tide.
Fleet-wide failure rate: The same presubmit job passed on 3/3 other PR runs in the last 30 days (100%, n=3; small sample). For the exact test, recent 7-day Sippy results report 97.6% overall, 98.2% on AWS, and 97.6% for HyperShift/external; the current 4.22 report shows 98.6% (139/141), versus 97.3% (146/150) in the previous window.
Open regressions: None found for this exact test in 4.22; Sippy reports open_bugs=0.
Linked bugs: No open linked bug is shown in the exact-test Sippy report (open_bugs=0).
Overlap assessment: The PR promotes VSphereMultiVCenterDay2 and updates vSphere-specific CRD validation and feature-gate data. The failed check is an AWS HyperShift control-plane upgrade test; no direct or indirect overlap with the changed vSphere surface was identified.
Missing-coverage risk: Low for the PR's vSphere change given the passing vSphere e2e and schema/feature-promotion checks. This override does not establish that the HyperShift upgrade path is healthy; it waives this unrelated failure for this PR.
Prior bot activity on this SHA: One /test e2e-aws-ovn-hypershift was issued at 19:37:50Z and produced this failed run; no prior override.
Decision and action: Override this failure as unrelated to the PR, based on the repeated test-level restart failure signal, current passing checks for the changed surface, and lack of overlap.

If you disagree with this assessment, rerun the job on the current revision with /test e2e-aws-ovn-hypershift.

---

AI-generated. Review for accuracy.

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.

[openshift-ci]

@vr4manta: The following tests 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/prow/e2e-aws-ovn-hypershift	00d3824	link	true	/test e2e-aws-ovn-hypershift
ci/prow/e2e-aws-ovn-hypershift-conformance	00d3824	link	true	/test e2e-aws-ovn-hypershift-conformance

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.

[vr4manta]

/retest

[redhat-chai-bot]

The /retest request has queued the required ci/prow/e2e-aws-ovn-hypershift-conformance run for this PR. It is currently pending: https://prow.ci.openshift.org/view/gs/test-platform-results-public/pr-logs/pull/openshift_api/3101/pull-ci-openshift-api-release-4.22-e2e-aws-ovn-hypershift-conformance/2110692398081249280. I did not post a second retest command.

---

AI-generated. Review for accuracy.

[vr4manta]

/payload-job periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-vsphere-ovn-upgrade

[openshift-ci]

@vr4manta: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-vsphere-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d2e78f40-c891-11f1-9668-5afc7f1666a6-0

[vr4manta]

This PR is not allowed to merge until the 5.0 variant merges: #3015. It cannot merge until after 5.0 GAs.