Bug 1846177
Summary: | Unable to upgrade OCP4.3.19 to OCP4.4 in disconnected env: CVO enters reconciling mode without applying any manifests in update mode | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
Component: | Cluster Version Operator | Assignee: | W. Trevor King <wking> |
Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 4.3.z | CC: | aos-bugs, jiajliu, jialiu, jokerman, mfuruta |
Target Milestone: | --- | ||
Target Release: | 4.2.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: The Cluster Version Operator had a race where it would consider a timed-out update reconciliation cycle as a successful update. The race was very rare, except for restricted-network clusters where the operator timed out attempting to fetch release image signatures.
Consequence: The Cluster Version Operator would enter its shuffled-manifest reconciliation mode, possibly breaking the cluster if the manifests were applied in an order that the components could not handle.
Fix: The Cluster Version Operator now treats those timed-out updates as failures.
Result: The Cluster Version Operator no longer enters reconciling mode before the update succeeds.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-01 16:08:23 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: | 1844117 | ||
Bug Blocks: |
Description
OpenShift BugZilla Robot
2020-06-11 00:49:06 UTC
Verified this bug with 4.2.0-0.nightly-2020-06-21-204910, PASS. Install a disconnected cluster with 4.2.0-0.nightly-2020-06-21-204910, trigger upgrade towards 4.3.26, upgrade is completed successfully. 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, 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/RHBA-2020:2589 |