Bug 1813998
| Summary: | Cloud Credential Operator pod crashlooping with golang segfault | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | W. Trevor King <wking> | |
| Component: | Cloud Credential Operator | Assignee: | Joel Diaz <jdiaz> | |
| Status: | CLOSED ERRATA | QA Contact: | wang lin <lwan> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.4 | CC: | bbrownin, cblecker, ccoleman, jdiaz, lmohanty, lwan, nmalik, pkanthal, suchaudh, vrutkovs, wking | |
| Target Milestone: | --- | Keywords: | Upgrades | |
| Target Release: | 4.4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: Cloud credential operator could crash loop when the original cluster was installed with OpenShift 4.1
Consequence: CCO would be unable to reconcile the permissions requests found in the CredentialsRequest objects.
Fix: Do not assume that parts of the Infrastructure fields are available.
Result: CCO can work with clusters that were originally installed with OpenShift 4.1.
|
Story Points: | --- | |
| Clone Of: | 1813343 | |||
| : | 1816704 (view as bug list) | Environment: | ||
| Last Closed: | 2020-05-04 11:46:27 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: | 1813343 | |||
| Bug Blocks: | 1816704 | |||
|
Description
W. Trevor King
2020-03-16 17:48:44 UTC
Based on the impacted edges above, the verification plan for the 4.4 fix is going to be: 1. Install a 4.1 cluster. Looks like 4.1.34 is a good choice because we recommend 4.1.24 -> 4.2.20 in stable-4.2. 2. Update to 4.2.20 (avoiding 4.2.21+ having the broken assumption that PlatformStatus is populated). 3. Update to 4.3.2 (avoid 4.3.3+ having the broken assumption that PlatformStatus is populated). We don't have any recommended edges into 4.3.2, [1] lists the motivating bugs, but none of them should actually break the update. 4. Force an update to the 4.4 nightly with the candidate fix. 5. Ensure the cred operator is not panicking. [1]: https://github.com/openshift/cincinnati-graph-data/blob/dc2a3c4cd879b0eeb7153c50f8706ad45166e8ac/blocked-edges/4.3.2.yaml#L1 Similar verification plan for the related registry-operator issue in [1]. If this fix lands first, and you attempt verification before the registry operator also lands a fix, you can ignore a panicking registry operator (or otherwise complaining, I'm not actually clear on how graciously it accepts the lack of install-config fallback) for the purpose of verifying this cred-operator bug. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1808425#c5 *** Bug 1814328 has been marked as a duplicate of this bug. *** The upgrading process is: 4.1.24 -> 4.2.20 -> 4.3.0 -> 4.4.0-0.nightly-2020-03-24-225110 Although there are some other cluster operators have not yet rolled out when cluster upgraded from 4.3.0 to 4.4.0-0.nightly-2020-03-24-225110, CCO can upgrade successfully. CCO won't panic when infrastructure .status has only platform field. 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:0581 |