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] AUTH-483: 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
Copy link
Contributor

openshift-ci bot commented Apr 29, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants