Once Bug 1995387 has been fixed and the base image for the tests is available, the test started showing legit failures. Job history (relevant jobs AFTER Aug 21): https://prow.ci.openshift.org/job-history/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-openstack-upgrade One example failure: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-openstack-upgrade/1429521411877113856 In particular, ETCD seems to not be healthy.
Tests seem to be still failing...
We still need to investigate why this job is failing. Still high prio.
Analyzing this job - https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-openstack-upgrade/1434468962166378496 PromeCIeus shows that: * at 13:05 etcd commit duration and wal sync times on .163 node spiked * at approx. the same time different node - .32 - shows increased network round trip time Seems infra is responsible for this
Wonder if https://github.com/openshift/machine-config-operator/pull/2782 wouldn't help there, cf https://bugzilla.redhat.com/show_bug.cgi?id=2002121.
Removing the Triaged keyword because: * the QE automation assessment (flag qe_test_coverage) is missing
*** Bug 2077270 has been marked as a duplicate of this bug. ***
We've integrated support for scheduled CI tasks with jitter into upstream Kubernetes CI infra and shouldn't be seeing this anymore. Closing as CURRENTRELEASE. We can open new bugs if this pops up again.