Forrest Babcock
Forrest Babcock
/lgtm /hold unhold when you are ready
Don't feel like we want to bring these in. There were [changes](https://github.com/openshift/origin/pull/28944) and a [revert](https://github.com/openshift/origin/pull/28977) that may have impacted these. ``` openshift-api-http2-service-network-reused-connections 4.17 amd64 ovn aws ha 118 13m42.1s 822000.00%...
/payload-aggregate periodic-ci-openshift-release-master-ci-4.17-upgrade-from-stable-4.16-e2e-azure-ovn-upgrade 10
Yeah there are failures in both jobs. Every run in [4.17-upgrade-from-stable-4.16-e2e-azure-ovn-upgrade](https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregator-periodic-ci-openshift-release-master-ci-4.17-upgrade-from-stable-4.16-e2e-azure-ovn-upgrade/1820890581816053760) is well over 10k. I wonder if the extra logging is stressing the disks. Probably need to try to...
/payload-aggregate periodic-ci-openshift-release-master-ci-4.17-e2e-aws-upgrade-ovn-single-node 10
/payload-aggregate periodic-ci-openshift-release-master-ci-4.17-e2e-aws-upgrade-ovn-single-node 10
I think SNO looks better, we don't see the duplicated disruption in the conformance run. The [aggregated disruption](https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregator-periodic-ci-openshift-release-master-ci-4.17-e2e-aws-upgrade-ovn-single-node/1823458192508588032) fails but we are in the process of removing sno aggregated disruption...
/test e2e-aws-ovn-single-node-upgrade