Skip to content

[release-4.15] OCPBUGS-25798: Deprecation snapshot backport#666

Closed
dtfranz wants to merge 1 commit intoopenshift:release-4.15from
dtfranz:deprecation-snapshot-backport
Closed

[release-4.15] OCPBUGS-25798: Deprecation snapshot backport#666
dtfranz wants to merge 1 commit intoopenshift:release-4.15from
dtfranz:deprecation-snapshot-backport

Conversation

@dtfranz
Copy link
Copy Markdown
Contributor

@dtfranz dtfranz commented Jan 23, 2024

Cherry-pick of #654

…ratorGroup. (#3149)

Signed-off-by: Daniel Franz <dfranz@redhat.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 8eb16f7a9e12be729e07207983d27af78c23695b
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jan 23, 2024
@openshift-ci-robot
Copy link
Copy Markdown

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-24526 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-24526 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

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

Details

In response to this:

Cherry-pick of #654

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.

@kevinrizza
Copy link
Copy Markdown
Member

/lgtm
/approve

@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 23, 2024
@dtfranz
Copy link
Copy Markdown
Contributor Author

dtfranz commented Jan 23, 2024

Looks like cluster creation failure.
/retest

@dtfranz
Copy link
Copy Markdown
Contributor Author

dtfranz commented Jan 24, 2024

We're running into test flakes now that have yet to be backported. I'll give this one more shot, but otherwise we'll need to wait for that to get this in.
/test e2e-gcp-olm

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor

/label cherry-pick-approved
/label qe-approved

@openshift-ci openshift-ci Bot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. qe-approved Signifies that QE has signed off on this PR labels Jan 24, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@dtfranz: This pull request references Jira Issue OCPBUGS-25798, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-24526 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-24526 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

Details

In response to this:

Cherry-pick of #654

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.

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor

test success, detail https://issues.redhat.com/browse/OCPBUGS-25798

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 24, 2024

@dtfranz: The following test 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-gcp-olm 6aba164 link true /test e2e-gcp-olm

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/test-infra repository. I understand the commands that are listed here.

@dtfranz
Copy link
Copy Markdown
Contributor Author

dtfranz commented Jan 26, 2024

Merged in #670; closing.

@dtfranz dtfranz closed this Jan 26, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@dtfranz: This pull request references Jira Issue OCPBUGS-25798. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

Cherry-pick of #654

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.

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-moderate Referenced Jira bug's severity is moderate 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. 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