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

[release-4.15] OCPBUGS-34674: Add a monitor test to check the existence of required-scc annotation in platform workloads #28754

Open
wants to merge 1 commit into
base: release-4.15
Choose a base branch
from

Conversation

liouk
Copy link
Member

@liouk liouk commented Apr 29, 2024

This is a manual cherry pick of #28660.

@openshift-ci openshift-ci bot requested review from jwforres and mfojtik April 29, 2024 09:22
@liouk
Copy link
Member Author

liouk commented Apr 29, 2024

/retitle WIP: [release-4.15] AUTH-483: Add a monitor test to check the existence of required-scc annotation in platform workloads

@openshift-ci openshift-ci bot changed the title monitortests: test existence of required-scc annotation in platform workloads WIP: [release-4.15] AUTH-483: Add a monitor test to check the existence of required-scc annotation in platform workloads Apr 29, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 29, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 29, 2024

@liouk: This pull request references AUTH-483 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 task to target either version "4.15." or "openshift-4.15.", but it targets "openshift-4.16" instead.

In response to this:

This is a manual cherry pick of #28660.

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 29, 2024
@liouk
Copy link
Member Author

liouk commented Apr 29, 2024

/retest

Copy link
Contributor

openshift-ci bot commented Apr 29, 2024

@liouk: 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/e2e-aws-etcd-recovery 3181727 link false /test e2e-aws-etcd-recovery
ci/prow/e2e-aws-ovn-single-node-serial 3181727 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node-upgrade 3181727 link false /test e2e-aws-ovn-single-node-upgrade

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.

@liouk liouk changed the title WIP: [release-4.15] AUTH-483: Add a monitor test to check the existence of required-scc annotation in platform workloads [release-4.15] AUTH-483: Add a monitor test to check the existence of required-scc annotation in platform workloads Apr 30, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 30, 2024
@ibihim
Copy link
Contributor

ibihim commented May 30, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 30, 2024
@deads2k deads2k added 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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels May 30, 2024
Copy link
Contributor

openshift-ci bot commented May 30, 2024

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: ibihim, liouk

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

@liouk liouk changed the title [release-4.15] AUTH-483: Add a monitor test to check the existence of required-scc annotation in platform workloads [release-4.15] OCPBUGS-34674: Add a monitor test to check the existence of required-scc annotation in platform workloads May 30, 2024
@openshift-ci-robot
Copy link

@liouk: This pull request references Jira Issue OCPBUGS-34674, which is invalid:

  • expected the bug to target the "4.15.z" version, but no target version was set
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
  • expected Jira Issue OCPBUGS-34674 to depend on a bug targeting a version in 4.16.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

This is a manual cherry pick of #28660.

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 30, 2024
@liouk
Copy link
Member Author

liouk commented May 30, 2024

/jira refresh

@openshift-ci-robot
Copy link

@liouk: This pull request references Jira Issue OCPBUGS-34674, which is invalid:

  • expected Jira Issue OCPBUGS-34674 to depend on a bug targeting a version in 4.16.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

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.

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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.

None yet