origin
origin copied to clipboard
openshift
[release-4.14] e2e node label test to verify blocking forbidden labels
/hold it for https://github.com/openshift/oc/pull/1571 and it's backport to 4.14 merge.
@rphillips: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]
In response to this:
/label backport-risk-assessed
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}
@jfrancoa: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]
In response to this:
/label cherry-pick-approved
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 APPROVED
Approval requirements bypassed by manually added approval.
This pull-request has been approved by: harche, rphillips
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Contains the code from, https://github.com/openshift/origin/pull/28296 and https://github.com/openshift/origin/pull/28499
@harche: 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 | 8c71b09ecd092a10700a0191ecb693ddd5488e7e | link | false | /test e2e-aws-etcd-recovery |
| ci/prow/e2e-openstack-ovn | 8c71b09ecd092a10700a0191ecb693ddd5488e7e | link | false | /test e2e-openstack-ovn |
| ci/prow/e2e-aws-ovn-single-node-serial | 8c71b09ecd092a10700a0191ecb693ddd5488e7e | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-gcp-ovn-rt-upgrade | 8c71b09ecd092a10700a0191ecb693ddd5488e7e | link | false | /test e2e-gcp-ovn-rt-upgrade |
| ci/prow/e2e-aws-ovn-single-node-upgrade | 8c71b09ecd092a10700a0191ecb693ddd5488e7e | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-aws-ovn-upgrade | 8c71b09ecd092a10700a0191ecb693ddd5488e7e | link | false | /test e2e-aws-ovn-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
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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-sigs/prow repository.