origin
origin copied to clipboard
openshift
NO-JIRA: drop ocp-storage exceptions for termination policy
Follow up to https://github.com/openshift/origin/pull/28777
This drops the exceptions that should be fixed by:
https://github.com/openshift/cluster-storage-operator/pull/470 https://github.com/openshift/vmware-vsphere-csi-driver-operator/pull/231 https://github.com/openshift/ibm-vpc-block-csi-driver-operator/pull/114
I'm hoping the presubmit jobs will tell us that they really are fixed.
/cc @deads2k @jsafrane /test all
@dobsonj: This pull request explicitly references no jira issue.
In response to this:
Follow up to https://github.com/openshift/origin/pull/28777
This drops the exceptions that should be fixed by:
https://github.com/openshift/cluster-storage-operator/pull/470 https://github.com/openshift/vmware-vsphere-csi-driver-operator/pull/231 https://github.com/openshift/ibm-vpc-block-csi-driver-operator/pull/114
I'm hoping the presubmit jobs will tell us that they really are fixed.
/cc @deads2k @jsafrane /test all
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: deads2k, dobsonj, jsafrane
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [deads2k]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
/retest-required
Remaining retests: 0 against base HEAD 56c34134788b53a5a60665e2412c991ba47392c4 and 2 for PR HEAD 85b1fdd7347c50b7b4131a91934938bfe8a4e2f0 in total
@dobsonj: 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-metal-ipi-sdn | da7a8991edf8f7fbef3e1359c88fa25a6c780616 | link | false | /test e2e-metal-ipi-sdn |
| ci/prow/e2e-aws-ovn-single-node-upgrade | 85b1fdd7347c50b7b4131a91934938bfe8a4e2f0 | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-openstack-ovn | 85b1fdd7347c50b7b4131a91934938bfe8a4e2f0 | link | false | /test e2e-openstack-ovn |
| ci/prow/e2e-aws-ovn-ipsec-serial | 85b1fdd7347c50b7b4131a91934938bfe8a4e2f0 | link | false | /test e2e-aws-ovn-ipsec-serial |
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-sigs/prow repository. I understand the commands that are listed here.
Job Failure Risk Analysis for sha: 85b1fdd7347c50b7b4131a91934938bfe8a4e2f0
| Job Name | Failure Risk |
|---|---|
| pull-ci-openshift-origin-master-e2e-aws-ovn-edge-zones | IncompleteTests Tests for this run (101) are below the historical average (1582): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems) |
| pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade | Medium [sig-network] pods should successfully create sandboxes by adding pod to network This test has passed 95.26% of 2005 runs on release 4.18 [Overall] in the last week. Open Bugs s390x: [sig-network] pods should successfully create sandboxes by adding pod to network fails with error adding pod to CNI network |
