Bug 1838810
Summary: | the read-only CR cannot be reconciled after removing the root cloud creds | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
Component: | Cloud Credential Operator | Assignee: | Joel Diaz <jdiaz> |
Status: | CLOSED ERRATA | QA Contact: | wang lin <lwan> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.5 | CC: | dgoodwin, knewcome, lwan, ngreen |
Target Milestone: | --- | ||
Target Release: | 4.4.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: The cloud-credential-operator had special-case handling for the CCO's own read-only CredentialsRequest CR that required the existence of the cloud root creds.
Consequence: If the cloud root creds are missing, CCO would be unable to reconcile CCO's own read-only CredentialsRequest CR.
Fix: Use the read-only CredentialsRequest credentials to validate the read-only CredentialsRequest just like every other CredentialsRequest.
Result: Removing the cloud root creds doesn't put CCO into a degraded state.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-06-17 22:26:36 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: | 1838718 | ||
Bug Blocks: |
Description
OpenShift BugZilla Robot
2020-05-21 20:26:39 UTC
This was bumped to high because this is blocking a customer deployment. The bug has been fixed. The test payload is 4.4.0-0.nightly-2020-06-07-075345 The result is as below: 1.Install OpenShift on AWS 2.wait for cco reconcile (it is about 6 hours) 3.The cco successes to reconcile the read-only credentials and don't Degraded $ oc get co cloud-credential NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE cloud-credential 4.4.0-0.nightly-2020-06-07-075345 True False False 8h 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:2445 |