Skip to content

[release-4.12] OCPBUGS-7556: Defuse E2e timebomb #449

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 3 commits into from
Feb 17, 2023

Conversation

grokspawn
Copy link
Contributor

This downstreams OCPBUGS-7102 and also disables this particular plugin since SCC is set to legacy and we are not enforcing PSA or labeling namespaces.

Signed-off-by: perdasilva <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: a3da4ea46d4bf5e704424893259ba5a0ae25d1e6
Signed-off-by: perdasilva <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: bb7b211
Signed-off-by: perdasilva <[email protected]>
Upstream-Repository: operator-lifecycle-manager
Upstream-commit: 4a28010
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2023

@grokspawn: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Defuse E2e timebomb

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.

@grokspawn grokspawn changed the title Defuse E2e timebomb [release-4.12] OCPBUGS-7556: Defuse E2e timebomb Feb 16, 2023
@openshift-ci-robot openshift-ci-robot added 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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Feb 16, 2023
@openshift-ci-robot
Copy link

@grokspawn: This pull request references Jira Issue OCPBUGS-7556, 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.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-7102 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-7102 targets the "4.13.0" version, which is one of the valid target versions: 4.13.0
  • bug has dependents

Requesting review from QA contact:
/cc @jianzhangbjz

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

In response to this:

This downstreams OCPBUGS-7102 and also disables this particular plugin since SCC is set to legacy and we are not enforcing PSA or labeling namespaces.

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

openshift-ci bot commented Feb 16, 2023

@grokspawn: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.12] OCPBUGS-7556: Defuse E2e timebomb

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.

@perdasilva
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, perdasilva

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 Feb 16, 2023
@perdasilva
Copy link
Contributor

/override ci/prow/verify

Author: perdasilva <[email protected]>
Date:   Tue Feb 7 14:42:32 2023 +0100
    remove csv labeler plugin timebomb test
    
    Signed-off-by: perdasilva <[email protected]>
    Upstream-Repository: operator-lifecycle-manager
    Upstream-commit: 4a28010aa5e5d35d182e9332ca200e7395ced312
[2023-02-16T15:48:21+0000]: downstream staging commit 3d1e4b9eafbcf43d19622dc4130f97e4d78f9c70 references an invalid number of repos: 0
[2023-02-16T15:48:21+0000]: staging commits must reference a single upstream repo

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2023

@perdasilva: Overrode contexts on behalf of perdasilva: ci/prow/verify

In response to this:

/override ci/prow/verify

Author: perdasilva <[email protected]>
Date:   Tue Feb 7 14:42:32 2023 +0100
   remove csv labeler plugin timebomb test
   
   Signed-off-by: perdasilva <[email protected]>
   Upstream-Repository: operator-lifecycle-manager
   Upstream-commit: 4a28010aa5e5d35d182e9332ca200e7395ced312
[2023-02-16T15:48:21+0000]: downstream staging commit 3d1e4b9eafbcf43d19622dc4130f97e4d78f9c70 references an invalid number of repos: 0
[2023-02-16T15:48:21+0000]: staging commits must reference a single upstream repo

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.

@jianzhangbjz
Copy link
Contributor

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

@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 Feb 17, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 17, 2023
@perdasilva
Copy link
Contributor

/retest

@perdasilva
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 17, 2023
@openshift-merge-robot openshift-merge-robot merged commit 01e8255 into openshift:release-4.12 Feb 17, 2023
@openshift-ci-robot
Copy link

@grokspawn: All pull requests linked via external trackers have merged:

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

In response to this:

This downstreams OCPBUGS-7102 and also disables this particular plugin since SCC is set to legacy and we are not enforcing PSA or labeling namespaces.

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

openshift-ci bot commented Feb 17, 2023

@grokspawn: 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/verify 3d1e4b9 link true /test verify

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
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

8 participants