openshift
[release-4.8] Bug 2107176: test: switch to testing CapBnd over CapInh
This is an automated cherry-pick of #27279
/assign haircommander
@openshift-cherrypick-robot: Bugzilla bug 2101429 has been cloned as Bugzilla bug 2107176. Retitling PR to link against new bug. /retitle [release-4.8] Bug 2107176: test: switch to testing CapBnd over CapInh
In response to this:
[release-4.8] Bug 2101429: test: switch to testing CapBnd over CapInh
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[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@openshift-cherrypick-robot: This pull request references Bugzilla bug 2107176, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target release (4.8.z) matches configured target release for branch (4.8.z)
- bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
- dependent bug Bugzilla bug 2101429 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
- dependent Bugzilla bug 2101429 targets the "4.9.z" release, which is one of the valid target releases: 4.9.0, 4.9.z
- bug has dependents
No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request.
In response to this:
[release-4.8] Bug 2107176: test: switch to testing CapBnd over CapInh
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.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: openshift-cherrypick-robot
To complete the pull request process, please assign bparees after the PR has been reviewed.
You can assign the PR to them by writing /assign @bparees in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@openshift-cherrypick-robot: 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-aws-upgrade | 22bbecace292145fc2e97e826ad6689b41f24fdc | link | true | /test e2e-aws-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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
@haircommander: Closed this PR.
In response to this:
/close
we won't move forward with this in 4.8
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-cherrypick-robot: This pull request references Bugzilla bug 2107176. The bug has been updated to no longer refer to the pull request using the external bug tracker.
In response to this:
[release-4.8] Bug 2107176: test: switch to testing CapBnd over CapInh
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.