let's see if the timeout increase improves the situation
most recent job passed https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-metal-ipi-upgrade-ovn-ipv6/1537200946411474944 still seeing the CVO flaky as one run failed, but the second went through we'll wait for the next job to see if the change is consistent
QA have nothing to do here as this is not QA CI, and there is nothing that I can do at this point. @Riccardo Pittau if you find that the job is working well for you, feel free to set to VERIFIED.
"[sig-cluster-lifecycle] Cluster version operator acknowledges upgrade " test seems to pass always with the new timeout in the Baremetal part, while the fixed 2 minutes timeout still fails, as expected
looking at the latest results the timeout increase made things better I'm going to verify this and check to see if we'll have to increase the general timeout value as well or use the baremetal one instead
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069