openshift
CNTRLPLANE-1437: add monitor test for checking default service account in pods (static test name)
Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.
For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.
This repository is configured in: automatic mode
@ehearne-redhat: This pull request references CNTRLPLANE-1437 which is a valid jira issue.
In response to this:
See #30262 for reference.
In response to #30557 .
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.
Scheduling required tests: /test e2e-aws-csi /test e2e-aws-ovn-fips /test e2e-aws-ovn-microshift /test e2e-aws-ovn-microshift-serial /test e2e-aws-ovn-serial-1of2 /test e2e-aws-ovn-serial-2of2 /test e2e-gcp-csi /test e2e-gcp-ovn /test e2e-gcp-ovn-upgrade /test e2e-metal-ipi-ovn-ipv6 /test e2e-vsphere-ovn /test e2e-vsphere-ovn-upi
Job Failure Risk Analysis for sha: 50d5f8af207ca011234ca84941c0cd196f7b1152
| Job Name | Failure Risk |
|---|---|
| pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6 | IncompleteTests Tests for this run (20) are below the historical average (3012): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems) |
Risk analysis has seen new tests most likely introduced by this PR. Please ensure that new tests meet guidelines for naming and stability.
New tests seen in this PR at sha: 50d5f8af207ca011234ca84941c0cd196f7b1152
- "[Monitor:no-default-service-account-operator-checker][sig-auth] all pods must not use the default service account." [Total: 6, Pass: 6, Fail: 0, Flake: 4]
![openshift-trt[bot] avatar](https://avatars.githubusercontent.com/u/111778100?v=4 "Published by a pub.dev verified publisher"){kind=small}
Scheduling required tests: /test e2e-aws-csi /test e2e-aws-ovn-fips /test e2e-aws-ovn-microshift /test e2e-aws-ovn-microshift-serial /test e2e-aws-ovn-serial-1of2 /test e2e-aws-ovn-serial-2of2 /test e2e-gcp-csi /test e2e-gcp-ovn /test e2e-gcp-ovn-upgrade /test e2e-metal-ipi-ovn-ipv6 /test e2e-vsphere-ovn /test e2e-vsphere-ovn-upi
Scheduling required tests: /test e2e-aws-csi /test e2e-aws-ovn-fips /test e2e-aws-ovn-microshift /test e2e-aws-ovn-microshift-serial /test e2e-aws-ovn-serial-1of2 /test e2e-aws-ovn-serial-2of2 /test e2e-gcp-csi /test e2e-gcp-ovn /test e2e-gcp-ovn-upgrade /test e2e-metal-ipi-ovn-ipv6 /test e2e-vsphere-ovn /test e2e-vsphere-ovn-upi
@ehearne-redhat It might be worth attempting a payload aggregate run with these changes to ensure that we don't run into the aggregation issues again.
@ehearne-redhat: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
- e2e-azure-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9450d410-d1e0-11f0-882c-a218c0bbc32d-0
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@ehearne-redhat: aborted active payload jobs for pull request openshift/origin#30561
/payload-aggregate periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-azure-ovn-upgrade 5
@ehearne-redhat: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
- periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-azure-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/dc712f10-d1e0-11f0-8d8b-d2f1bf1f9557-0
@everettraven - I checked the aggregate tests and I did not see any unique namespace names.
@ehearne-redhat feel free to add the verified label and ping the appropriate TRT folks for a re-review here :)
@ehearne-redhat: This PR has been marked as verified by @ehearne-redhat.
In response to this:
/verified by @ehearne-redhat
/assign @stbenjam @xueqzhan
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.
@stbenjam @xueqzhan feel free to take a look when you have a chance :)
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ehearne-redhat, everettraven, xueqzhan
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [xueqzhan]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest-required
Remaining retests: 0 against base HEAD 89d0a8789661d980960d574cf8f01892a5ac006b and 2 for PR HEAD 7073eae36726388c019e67c32ad18a9f8f94833c in total