origin
origin copied to clipboard
openshift
EgressQoS downstream tests for OVN Kubernetes
/payload 4.12 nightly blocking
I'd just like to see how this does on release payloads before merging, if that's OK.
@stbenjam: trigger 6 job(s) of type blocking for the nightly release of OCP 4.12
- periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-sdn-upgrade
- periodic-ci-openshift-release-master-ci-4.12-e2e-azure-ovn-upgrade
- periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-gcp-ovn-upgrade
- periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-sdn-serial
- periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-ovn-ipv6
- periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-sdn-bm
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9a497f10-507f-11ed-9570-6043d98ed457-0
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dcbw, jcaamano, oribon, stbenjam
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [stbenjam]
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 6f17d51fd4b5a89e36c50b43ddad42e43f2d08ba and 2 for PR HEAD 2ad09e0a23443005301de9f6079b15ed28efb240 in total
@oribon: 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-ovn-single-node-serial | 5ad0ed9e0098787985567e8bcc1be202ee42d05a | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-openstack-ovn | 5ad0ed9e0098787985567e8bcc1be202ee42d05a | link | false | /test e2e-openstack-ovn |
| ci/prow/e2e-aws-csi | 5ad0ed9e0098787985567e8bcc1be202ee42d05a | link | false | /test e2e-aws-csi |
| ci/prow/e2e-agnostic-ovn-cmd | 5ad0ed9e0098787985567e8bcc1be202ee42d05a | link | false | /test e2e-agnostic-ovn-cmd |
| ci/prow/e2e-aws-ovn-single-node-upgrade | 5ad0ed9e0098787985567e8bcc1be202ee42d05a | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-gcp-ovn-rt-upgrade | 5ad0ed9e0098787985567e8bcc1be202ee42d05a | link | false | /test e2e-gcp-ovn-rt-upgrade |
| ci/prow/e2e-aws-ovn-single-node | 5ad0ed9e0098787985567e8bcc1be202ee42d05a | link | false | /test e2e-aws-ovn-single-node |
| ci/prow/e2e-gcp-ovn-image-ecosystem | 5ad0ed9e0098787985567e8bcc1be202ee42d05a | link | true | /test e2e-gcp-ovn-image-ecosystem |
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.
@oribon: 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-gcp-ovn-image-ecosystem | 5ad0ed9e0098787985567e8bcc1be202ee42d05a | link | true | /test e2e-gcp-ovn-image-ecosystem |
| ci/prow/e2e-aws-ovn-single-node | e5a0a81682f4e3e5a33783eb9d9cca56ebf67fb4 | link | false | /test e2e-aws-ovn-single-node |
| ci/prow/e2e-openstack-ovn | e5a0a81682f4e3e5a33783eb9d9cca56ebf67fb4 | link | false | /test e2e-openstack-ovn |
| ci/prow/e2e-aws-ovn-single-node-serial | e5a0a81682f4e3e5a33783eb9d9cca56ebf67fb4 | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-aws-ovn-single-node-upgrade | e5a0a81682f4e3e5a33783eb9d9cca56ebf67fb4 | 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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dcbw, jcaamano, oribon, stbenjam
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [stbenjam]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/hold
these tests flake sometimes due to some other test crashing ovnk (external gw), pretty confident that on themselves they work properly (ran them a couple of times on a cluster-bot with no problem). Since there is no rush in getting this in we'll hold merging this to not expand the flake surface @pperiyasamy @jcaamano
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
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
PR needs rebase.
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.
