Bug 2100964 - The ccoctl does not seem to know how to leverage the VMs service account to talk to GCP APIs.
Summary: The ccoctl does not seem to know how to leverage the VMs service account to t...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Credential Operator
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Akhil Rane
QA Contact: Jianping SHu
Depends On:
Blocks: 2105468
TreeView+ depends on / blocked
Reported: 2022-06-24 19:34 UTC by Vinu K
Modified: 2022-10-10 04:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-07-20 07:46:10 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cloud-credential-operator pull 475 0 None open Bug 2100964: Make ccoctl work with credentials fetched from gcloud cli defaults 2022-07-06 05:05:51 UTC
Red Hat Product Errata RHBA-2022:5568 0 None None None 2022-07-20 07:46:27 UTC

Description Vinu K 2022-06-24 19:34:01 UTC
Description of problem:
The ccoctl throws the below errow while running without a GCP SA key.
2022/06/20 16:14:59 Credentials loaded from gcloud CLI defaults
2022/06/20 16:14:59 Failed to initiate GCP client: unexpected end of JSON input

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

How reproducible:

Steps to Reproduce:
1. Run the below without GCP SA key.
ccoctl gcp create-all \
--name=<name> \
--region=<gcp_region> \
--project=<gcp_project_id> \

Actual results:
Not able to create GCP resources with the Cloud Credential Operator utility.

Expected results:
Created GCP resources with the Cloud Credential Operator utility.

Additional info:

Comment 9 errata-xmlrpc 2022-07-20 07:46:10 UTC
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 (OpenShift Container Platform 4.10.23 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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