Bug 1753036 - failed to get cloud credentials from secret /: secrets \"cloud-credentials\" not found
Summary: failed to get cloud credentials from secret /: secrets \"cloud-credentials\" ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Credential Operator
Version: 4.2.0
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
: 4.3.0
Assignee: Devan Goodwin
QA Contact: Oleg Nesterov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-17 21:53 UTC by acossett
Modified: 2019-10-28 12:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 17:20:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Output of must-gather with cloud-credentials error (9.25 MB, application/x-bzip)
2019-10-28 12:16 UTC, Joel Pearson
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer issues 2334 0 'None' closed Azure OpenShift Installer issue 2021-01-18 15:56:23 UTC

Description acossett 2019-09-17 21:53:07 UTC
Description of problem:

error": "failed to get cloud credentials from secret /: secrets \"cloud-credentials\" not found

Version-Release number of selected component (if applicable):

4.2.latest nightly build

How reproducible:

Always for customer

Steps to Reproduce:
1.Deploy OCP on GCP with UPI instruction.
2.
3.

Actual results:
cloud-credentials are not created on GCP Installation into openshift-ingress-operator project

Expected results:
cloud-credentials to be created by the installer

Additional info:

../oc logs ingress-operator-7b899bc5c4-4jl7k
2019-09-17T20:32:17.668Z        INFO    operator        log/log.go:26   started zapr logger
2019-09-17T20:32:19.637Z        INFO    operator.entrypoint     ingress-operator/main.go:62     using operator namespace        {"namespace": "openshift-ingress-operator"}
2019-09-17T20:32:19.653Z        ERROR   operator.entrypoint     ingress-operator/main.go:105    failed to create DNS manager    {"error": "failed to get cloud credentials from secret /: secrets \"cloud-credentials\" not found"}

Comment 1 Scott Dodson 2019-09-18 17:04:18 UTC
Please provide `oc adm must-gather` as an attachment.

Comment 2 acossett 2019-09-19 16:07:28 UTC
Version used
http://mirror.openshift.com/pub/openshift-v4/clients/ocp-dev-preview/4.2.0-0.nightly-2019-09-16-114316/openshift-client-linux-4.2.0-0.nightly-2019-09-16-114316.tar.gz

The command use ask, is on it way, waiting on customer to provide the results.

Comment 11 Devan Goodwin 2019-10-22 17:20:01 UTC
We're going to close due to lack of info, if anyone can get this uploaded using the process linked above please re-open and we can take a look.

Comment 12 Joel Pearson 2019-10-28 12:16:25 UTC
Created attachment 1629750 [details]
Output of must-gather with cloud-credentials error

I have been trying to deploy an openshift 4.2.0 cluster in Azure using the regular installation approach, it has failed 3 times in a row.

I have attached the must-gather output from the latest attempt.

Comment 13 Devan Goodwin 2019-10-28 12:22:42 UTC
Hi Joel, this does not look related to the secret not being found as reported in this bug.

From your must-gather results: 2019-10-28T12:08:41.6625985Z time="2019-10-28T12:08:41Z" level=error msg="error syncing credentials: error syncing creds in mint-mode: unable to list AAD applications: graphrbac.ApplicationsClient#List: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code=\"Unknown\" Message=\"Unknown service error\" Details=[{\"odata.error\":{\"code\":\"Authorization_RequestDenied\",\"date\":\"2019-10-28T12:08:41\",\"message\":{\"lang\":\"en\",\"value\":\"Insufficient privileges to complete the operation.\"},\"requestId\":\"9cef4c38-c9bf-4d41-9b39-4bac0add8b22\"}}]" controller=credreq cr=openshift-cloud-credential-operator/openshift-image-registry-azure secret=openshift-image-registry/installer-cloud-credentials

Looks like your credentials used for install may need additional permissions, but this should be covered in the documentation.

Comment 14 Joel Pearson 2019-10-28 12:23:51 UTC
Oh, nice pickup, thanks.


Note You need to log in before you can comment on or make changes to this bug.