Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TRT-1563: Revert #1802 "Move config v1 IP validation to CEL" #1810

Merged

Conversation

dgoodwin
Copy link
Contributor

@dgoodwin dgoodwin commented Mar 15, 2024

Reverts #1802 ; tracked by TRT-1563

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

Change appears to have broken minor upgrades, now stalling unable to update the infrastructure resource.

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.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade

CC: @JoelSpeed

PR created by Revertomatic™️

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 15, 2024

@dgoodwin: This pull request references TRT-1563 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.16.0" version, but no target version was set.

In response to this:

Reverts #1802 ; tracked by TRT-1563

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

Change appears to have broken minor upgrades, now stalling unable to update the infrastructure resource.

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.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade

CC: @JoelSpeed

PR created by Revertomatic™️

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 15, 2024
Copy link
Contributor

openshift-ci bot commented Mar 15, 2024

Hello @dgoodwin! 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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 15, 2024

@dgoodwin: This pull request references TRT-1563 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.16.0" version, but no target version was set.

In response to this:

Reverts #1802 ; tracked by TRT-1563

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

Change appears to have broken minor upgrades, now stalling unable to update the infrastructure resource.

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.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade

CC: @JoelSpeed

PR created by Revertomatic™️

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 openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Mar 15, 2024
@dgoodwin
Copy link
Contributor Author

/override ci/prow/e2e-gcp
/override ci/prow/e2e-azure
/override ci/prow/e2e-aws-ovn
/override ci/prow/e2e-upgrade
/override ci/prow/e2e-aws-serial-techpreview
/override ci/prow/e2e-aws-serial
/override ci/prow/e2e-aws-ovn-techpreview
/override ci/prow/e2e-aws-ovn-hypershift

@stbenjam
Copy link
Member

/lgtm

@stbenjam
Copy link
Member

/label approved

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 15, 2024
Copy link
Contributor

openshift-ci bot commented Mar 15, 2024

@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e-aws-ovn, ci/prow/e2e-aws-ovn-hypershift, ci/prow/e2e-aws-ovn-techpreview, ci/prow/e2e-aws-serial, ci/prow/e2e-aws-serial-techpreview, ci/prow/e2e-azure, ci/prow/e2e-gcp, ci/prow/e2e-upgrade

In response to this:

/override ci/prow/e2e-gcp
/override ci/prow/e2e-azure
/override ci/prow/e2e-aws-ovn
/override ci/prow/e2e-upgrade
/override ci/prow/e2e-aws-serial-techpreview
/override ci/prow/e2e-aws-serial
/override ci/prow/e2e-aws-ovn-techpreview
/override ci/prow/e2e-aws-ovn-hypershift

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/test-infra repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 15, 2024
Copy link
Contributor

openshift-ci bot commented Mar 15, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

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 removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 15, 2024
@stbenjam
Copy link
Member

/label approved

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 15, 2024
@dgoodwin
Copy link
Contributor Author

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Mar 15, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 094bb9e into openshift:master Mar 15, 2024
17 checks passed
Copy link
Contributor

openshift-ci bot commented Mar 15, 2024

@dgoodwin: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra 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
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. 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. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants