Bug 1659979

Summary: Unable to add Google Cloud Platform as compute resource to Satellite.
Product: Red Hat Satellite 6 Reporter: Sagar Lutade <slutade>
Component: Compute Resources - GCEAssignee: Kavita <kgaikwad>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.3.4CC: ahumbe, bkearney, jenander, jyejare, kgaikwad, kindjal, mmccune
Target Milestone: 6.6.0Keywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 12:47:06 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: 1639696    
Bug Blocks:    

Description Sagar Lutade 2018-12-17 10:12:11 UTC
Description of problem:

When trying to add Google Cloud Platform as compute resource it fails to add.
The error is unable to save NOT found while selecting the option Load Zones.

Version-Release number of selected component (if applicable):
Satellite version 6.3 and 6.4

How reproducible:
By adding a new Compute resource to the Satellite.

Steps to Reproduce:
1.Login to Satellite web UI.
2.Infrastructure > Compute Resources > create new.
3.Input the details:

 Google Project ID *
 Client Email *
 Certificate path * (p12 file generate from the Google Cloud Platform console.)
4. Load Zones.

Actual results:
It should Load the Zones and create the resource.

Comment 5 kindjal 2019-01-11 21:38:24 UTC
I get "Unable to access key" when I try this.

Comment 13 Lukáš Hellebrandt 2019-07-16 08:25:30 UTC
Verified with Sat 6.6 snap 11. GCE account can be added and its VMs can be listed.

Comment 15 errata-xmlrpc 2019-10-22 12:47:06 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, and where to find the updated
files, follow the link below.

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