Bug 2100964

Summary:	The ccoctl does not seem to know how to leverage the VMs service account to talk to GCP APIs.
Product:	OpenShift Container Platform	Reporter:	Vinu K <vkochuku>
Component:	Cloud Credential Operator	Assignee:	Akhil Rane <arane>
Status:	CLOSED ERRATA	QA Contact:	Jianping SHu <jshu>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.10	CC:	bsmitley, lwan, mihuang, mworthin, wking
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-20 07:46:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	2105468

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):
v4u10

How reproducible:
100%

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


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.

https://access.redhat.com/errata/RHBA-2022:5568