Bug 2093992
Summary: | Cluster version operator acknowledges upgrade failing on periodic-ci-openshift-release-master-nightly-4.11-e2e-metal-ipi-upgrade-ovn-ipv6 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Devan Goodwin <dgoodwin> |
Component: | Bare Metal Hardware Provisioning | Assignee: | Riccardo Pittau <rpittau> |
Bare Metal Hardware Provisioning sub component: | cluster-baremetal-operator | QA Contact: | |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | derekh, jack.ottofaro, janders, jiajliu, lmohanty, rpittau, sippy, wking |
Version: | 4.11 | Keywords: | OtherQA, Triaged |
Target Milestone: | --- | ||
Target Release: | 4.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 2071998 | Environment: | |
Last Closed: | 2022-08-10 11:16:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2071998 | ||
Bug Blocks: | 2093987 |
Comment 4
Riccardo Pittau
2022-06-16 07:37:21 UTC
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 |