Details
-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
4.15.0
-
None
-
No
-
False
-
Description
Description of problem:
There is not sufficient evidence to establish a statistically significant trend, but TRT tooling is showing several concerning disruptions during vsphere minor upgrade tests.
Version-Release number of selected component (if applicable):
4.15
Additional info:
Jobs: 1. https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.15-upgrade-from-stable-4.14-e2e-vsphere-zones-upgrade/1739982515814273024 shows a 150 second host-to-host-reused-connections disruption. https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.15-upgrade-from-stable-4.14-e2e-vsphere-zones-upgrade/1739982515814273024/artifacts/e2e-vsphere-zones-upgrade/openshift-e2e-test/artifacts/junit/e2e-timelines_everything_20231227-130017.html shows the disruption @ 2023-12-27 2:04:53 due to "connection refused errors". The timeline shows the event correlating with a pending KubeDaemonSetRolloutStuck alert in openshift-multus. 2. https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.15-upgrade-from-stable-4.14-e2e-vsphere-upgrade/1742519342420987904 shows 94s of disruption in host-to-pod-new-connections . 3. https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.15-e2e-vsphere-ovn-etcd-scaling/1739982280404766720 shows 165s of disruption in host-to-host-new-connections and 153s of disruption in host-to-pod-new-connections .
