Skip to content

Conversation

@neisw
Copy link
Contributor

@neisw neisw commented Feb 1, 2026

Reverts #30525

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

4.22.0-0.nightly-2026-02-01-095950 is failing aggregated-aws-ovn-single-node-upgrade-4.22-micro due to failures caused by Conformance requires at least two nodes which won't work for single node.

Tracking the issue in TRT-2536

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

/payload-job periodic-ci-openshift-release-master-ci-4.22-e2e-aws-upgrade-ovn-single-node

CC: @mtulio

@openshift-ci-robot
Copy link

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 1, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 1, 2026

@neisw: This pull request references SPLAT-2337 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 either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Reverts #30525

4.22.0-0.nightly-2026-02-01-095950 failing aggregated-aws-ovn-single-node-upgrade-4.22-micro due to failures caused by Conformance requires at least two nodes which won't work for single node.

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.

@neisw
Copy link
Contributor Author

neisw commented Feb 1, 2026

/payload-job periodic-ci-openshift-release-master-ci-4.22-e2e-aws-upgrade-ovn-single-node

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2026

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

  • periodic-ci-openshift-release-master-ci-4.22-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2542d8c0-ff80-11f0-9a93-49c79f4e66e8-0

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 1, 2026
@openshift-ci openshift-ci bot requested review from deads2k and p0lyn0mial February 1, 2026 15:10
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 1, 2026

@neisw: This pull request references SPLAT-2337 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 either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Reverts #30525

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

4.22.0-0.nightly-2026-02-01-095950 is failing aggregated-aws-ovn-single-node-upgrade-4.22-micro due to failures caused by Conformance requires at least two nodes which won't work for single node.

Tracking the issue in TRT-2536

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

/payload-job periodic-ci-openshift-release-master-ci-4.22-e2e-aws-upgrade-ovn-single-node

CC: @mtulio

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.

@neisw
Copy link
Contributor Author

neisw commented Feb 1, 2026

/cc @mtulio

@openshift-ci openshift-ci bot requested a review from mtulio February 1, 2026 15:26
@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@mtulio
Copy link
Contributor

mtulio commented Feb 1, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mtulio, neisw

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

@neisw
Copy link
Contributor Author

neisw commented Feb 1, 2026

/verified by payload-job

We don't see the [cloud-provider-aws-e2e] failures

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 1, 2026
@openshift-ci-robot
Copy link

@neisw: This PR has been marked as verified by payload-job.

Details

In response to this:

/verified by payload-job

We don't see the [cloud-provider-aws-e2e] failures

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.

@neisw
Copy link
Contributor Author

neisw commented Feb 1, 2026

/override ci/prow/e2e-vsphere-ovn-upi
/override ci/prow/e2e-aws-ovn-fips
/override ci/prow/e2e-aws-ovn-serial-1of2

Unrelated failures

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2026

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-aws-ovn-fips, ci/prow/e2e-aws-ovn-serial-1of2, ci/prow/e2e-vsphere-ovn-upi

Details

In response to this:

/override ci/prow/e2e-vsphere-ovn-upi
/override ci/prow/e2e-aws-ovn-fips
/override ci/prow/e2e-aws-ovn-serial-1of2

Unrelated failures

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
Copy link
Contributor

openshift-ci bot commented Feb 1, 2026

@neisw: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit e3f443a into openshift:main Feb 1, 2026
20 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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants