Bug 1356299

Summary:	Service account in GCE Provider validates for spaces when it should not
Product:	Red Hat CloudForms Management Engine	Reporter:	Aparna Karve <akarve>
Component:	UI - OPS	Assignee:	Aparna Karve <akarve>
Status:	CLOSED ERRATA	QA Contact:	Shveta <sshveta>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.6.0	CC:	akarve, hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	cloud:provider
Fixed In Version:	5.7.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1372760 (view as bug list)		Environment:
Last Closed:	2017-01-04 12:57:26 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1372760

Description Aparna Karve 2016-07-13 22:38:38 UTC

Description of problem:Service account in GCE Provider validates for spaces when it should not


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


How reproducible:


Steps to Reproduce:
1. Add a GCE Cloud Provider
2. Enter JSON in the Service Account input field
3. 

Actual results:
"Spaces are prohibited" validation message appears

Expected results:
Service Account should ignore spaces, since spaces are expected

Additional info:

Comment 2 Satoe Imaishi 2016-08-18 20:30:22 UTC

Aparna, can you add PR link that fixed this issue?

Comment 3 Aparna Karve 2016-08-18 21:00:26 UTC

Satoe, here's the PR link - https://github.com/ManageIQ/manageiq/pull/9796

Comment 6 Shveta 2016-09-19 18:17:25 UTC

Fixed.
Verified in 5.7.0.0.20160906172503_12f65cb

Comment 8 errata-xmlrpc 2017-01-04 12:57:26 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.

https://rhn.redhat.com/errata/RHBA-2017-0012.html