Skip to content

OCPBUGS-52848: Revert "OCPBUGS-52346: bump x/oauth2 to version 0.27.0" #606

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

Merged
merged 1 commit into from
Mar 12, 2025

Conversation

xueqzhan
Copy link
Contributor

Reverts #602

Samples operator is the only one that is failing the nightly now and we are running out of ideas as to what could be the cause for this. We are reverting both #602 and #601 and see if that will make a difference with the official payload run. If proven unrelated, please unrevert this revert and have the change reintroduced to main.

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important 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 Mar 12, 2025
@openshift-ci-robot
Copy link
Contributor

@xueqzhan: This pull request references Jira Issue OCPBUGS-52346, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

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 #602

Samples operator is the only one that is failing the nightly now and we are running out of ideas as to what could be the cause for this. We are reverting both #602 and #601 and see if that will make a difference with the official payload run. If proven unrelated, please unrevert this revert and have the change reintroduced to main.

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 fbm3307 and shannon March 12, 2025 14:20
@aroyoredhat
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Mar 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aroyoredhat, xueqzhan

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

The pull request process is described 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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 12, 2025
@xueqzhan
Copy link
Contributor Author

/label docs-approved
/label px-approved
/label qe-approved

@openshift-ci openshift-ci bot added docs-approved Signifies that Docs has signed off on this PR px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR labels Mar 12, 2025
@xueqzhan xueqzhan changed the title Revert "OCPBUGS-52346: bump x/oauth2 to version 0.27.0" OCPBUGS-52848: Revert "OCPBUGS-52346: bump x/oauth2 to version 0.27.0" Mar 12, 2025
@openshift-ci-robot
Copy link
Contributor

@xueqzhan: This pull request references Jira Issue OCPBUGS-52848, which is invalid:

  • expected the bug to target the "4.19.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 #602

Samples operator is the only one that is failing the nightly now and we are running out of ideas as to what could be the cause for this. We are reverting both #602 and #601 and see if that will make a difference with the official payload run. If proven unrelated, please unrevert this revert and have the change reintroduced to main.

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.

@xueqzhan
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 Mar 12, 2025
@openshift-ci-robot
Copy link
Contributor

@xueqzhan: This pull request references Jira Issue OCPBUGS-52848, 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.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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

/retest-required

Remaining retests: 0 against base HEAD 66d76a1 and 2 for PR HEAD 9b8183c in total

Copy link
Contributor

openshift-ci bot commented Mar 12, 2025

@xueqzhan: 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/okd-scos-e2e-aws-ovn 9b8183c link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-proxy 9b8183c link false /test e2e-aws-ovn-proxy

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 9be05e7 into openshift:main Mar 12, 2025
9 of 11 checks passed
@openshift-ci-robot
Copy link
Contributor

@xueqzhan: Jira Issue OCPBUGS-52848: All pull requests linked via external trackers have merged:

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

In response to this:

Reverts #602

Samples operator is the only one that is failing the nightly now and we are running out of ideas as to what could be the cause for this. We are reverting both #602 and #601 and see if that will make a difference with the official payload run. If proven unrelated, please unrevert this revert and have the change reintroduced to main.

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

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-samples-operator
This PR has been included in build ose-cluster-samples-operator-container-v4.19.0-202503130217.p0.g9be05e7.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. docs-approved Signifies that Docs has signed off on this PR jira/severity-important Referenced Jira bug's severity is important 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. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants