-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
4.14, 4.15
-
None
-
No
-
Proposed
-
False
-
Description of problem:
The cloud-credential-operator-gcp-ro-creds should be used when connecting to the cloud api to determine if the credentialRequests need updating. However, recent changes appear to make this fail, and instead CCO falls back to the root credential.
Version-Release number of selected component (if applicable):
4.14, 4.15
How reproducible:
Always
Steps to Reproduce:
1. Install a gcp cluster using mint mode 2. Delete a cloud credential secret to trigger a sync
Actual results:
time="2023-11-07T20:55:01Z" level=warning msg="read-only creds not found, using root creds client" actuator=gcp cr=openshift-cloud-credential-operator/openshift-cloud-network-config-controller-gcp secret=openshift-cloud-credential-operator/cloud-credential-operator-gcp-ro-creds
Expected results:
time="2023-11-10T20:31:50Z" level=debug msg="creating read GCP client" actuator=gcp cr=openshift-cloud-credential-operator/openshift-ingress-gcp secret=openshift-cloud-credential-operator/cloud-credential-operator-gcp-ro-creds
Additional info:
- blocks
-
CCO-244 Update GCP Credentials Request manifest of the Cloud Credentials Operator to use new API field for requesting permissions
-
- Closed
-
- relates to
-
-
- Closed
-