Skip to content

Conversation

dgoodwin
Copy link
Contributor

Reverts #981 ; tracked by OCPBUGS-57519

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

First payload this arrived in showing some jobs experiencing hundreds of download container restarts

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-aggregate periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade 10

CC: @jhadvig

PR created by Revertomatic™️

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 17, 2025
@openshift-ci-robot
Copy link
Contributor

@dgoodwin: This pull request references Jira Issue OCPBUGS-57519, which is invalid:

  • expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Reverts #981 ; tracked by OCPBUGS-57519

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

First payload this arrived in showing some jobs experiencing hundreds of download container restarts

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-aggregate periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade 10

CC: @jhadvig

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 requested review from jhadvig and TheRealJon June 17, 2025 12:52
@dgoodwin
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 17, 2025
@openshift-ci-robot
Copy link
Contributor

@dgoodwin: This pull request references Jira Issue OCPBUGS-57519, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

In response to this:

/jira refresh

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 requested a review from yapei June 17, 2025 12:55
@dgoodwin
Copy link
Contributor Author

/override ci/prow/e2e-aws-console
/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/e2e-aws-ovn-single-node
/override ci/prow/e2e-gcp-ovn
/override ci/prow/okd-scos-e2e-aws-ovn
/override ci/prow/e2e-hypershift-conformance
/override ci/prow/e2e-aws-operator

Copy link
Contributor

openshift-ci bot commented Jun 17, 2025

@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e-aws-console, ci/prow/e2e-aws-operator, ci/prow/e2e-aws-ovn-single-node, ci/prow/e2e-azure-ovn-upgrade, ci/prow/e2e-gcp-ovn, ci/prow/e2e-hypershift-conformance, ci/prow/okd-scos-e2e-aws-ovn

In response to this:

/override ci/prow/e2e-aws-console
/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/e2e-aws-ovn-single-node
/override ci/prow/e2e-gcp-ovn
/override ci/prow/okd-scos-e2e-aws-ovn
/override ci/prow/e2e-hypershift-conformance
/override ci/prow/e2e-aws-operator

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.

@smg247
Copy link
Member

smg247 commented Jun 17, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 17, 2025
Copy link
Contributor

openshift-ci bot commented Jun 17, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dgoodwin, smg247
Once this PR has been reviewed and has the lgtm label, please assign therealjon for approval. For more information see the 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

@dgoodwin
Copy link
Contributor Author

/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 Jun 17, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 7904e3f into openshift:main Jun 17, 2025
12 checks passed
@openshift-ci-robot
Copy link
Contributor

@dgoodwin: Jira Issue OCPBUGS-57519: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-57519 has been moved to the MODIFIED state.

In response to this:

Reverts #981 ; tracked by OCPBUGS-57519

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

First payload this arrived in showing some jobs experiencing hundreds of download container restarts

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-aggregate periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade 10

CC: @jhadvig

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.

Copy link
Contributor

openshift-ci bot commented Jun 17, 2025

@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-sigs/prow repository. I understand the commands that are listed here.

@dgoodwin dgoodwin deleted the revert-981-1750164677322 branch June 17, 2025 13:52
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-console-operator
This PR has been included in build openshift-enterprise-console-operator-container-v4.20.0-202506171641.p0.g7904e3f.assembly.stream.el9.
All builds following this will include this PR.

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/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants