Bug 1649806 - Validation for GCE Provider Returns No Success/Failure in ManageIQ Hammer 1-rc1
Summary: Validation for GCE Provider Returns No Success/Failure in ManageIQ Hammer 1-rc1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: GA
: 5.10.0
Assignee: Bronagh Sorota
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-14 14:49 UTC by Noah Altunian
Modified: 2019-02-07 23:04 UTC (History)
11 users (show)

Fixed In Version: 5.10.0.25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 23:03:59 UTC
Category: ---
Cloudforms Team: GCE
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Shows the log entries in my production.lg file when validating GCE as a provider. (2.03 KB, text/plain)
2018-11-14 14:49 UTC, Noah Altunian
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0212 0 None None None 2019-02-07 23:04:04 UTC

Description Noah Altunian 2018-11-14 14:49:02 UTC
Created attachment 1505706 [details]
Shows the log entries in my production.lg file when validating GCE as a provider.

Description of problem:
On the `hammer-1-rc1' appliance, there's a bug when validating and adding Google Compute Engine as a Cloud Provider. After adding my GCE credentials and 'validating', no green/red flash message appears, and the 'Add' button remains grayed out.

In `production.log' the appliance receives a `200 OK' response when validating with GCE, yet `hammer-1-rc1' doesn't do anything with the returned authentication. I have attached the entries in my `production.log` file.

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

How reproducible:
This is reproducible by downloading and using the official Google appliance for ManageIQ version `hammer-1-rc1' and adding Google Compute Engine as a provider in `Compute -> Clouds -> Providers.'

Steps to Reproduce:
1. From the ManageIQ dashboard, go to Compute -> Clouds -> Providers
2. Navigate to Configuration -> Add a New Cloud Provider
3. For `Type', select Google Compute Engine. Add your credentials
4. Click `Validate'.

Actual results:
No green/red flash message indicating validation status.

Expected results:
A success or error message, with the ability to `Add' the provider if the validation was successful.

Additional info:
/var/www/miq/vmdb/log/log/production.log is of interest when troubleshooting this bug.

Comment 3 CFME Bot 2018-11-15 19:21:41 UTC
New commit detected on ManageIQ/manageiq-ui-classic/hammer:

https://github.com/ManageIQ/manageiq-ui-classic/commit/5b791abdf854d09518b35adf5092f70d35c262f3
commit 5b791abdf854d09518b35adf5092f70d35c262f3
Author:     Harpreet Kataria <hkataria>
AuthorDate: Thu Nov 15 11:43:56 2018 -0500
Commit:     Harpreet Kataria <hkataria>
CommitDate: Thu Nov 15 11:43:56 2018 -0500

    Merge pull request #4911 from AparnaKarve/fix_gce_validation

    Fix GCE validation

    (cherry picked from commit 158b6aa77db8e5b51be1a4deecbe6d7e318a9a55)

    https://bugzilla.redhat.com/show_bug.cgi?id=1649806

 app/assets/javascripts/controllers/ems_common/ems_common_form_controller.js | 4 +
 app/controllers/mixins/ems_common_angular.rb | 1 +
 spec/javascripts/controllers/ems_common/ems_common_form_controller_spec.js | 12 +
 3 files changed, 17 insertions(+)

Comment 4 Ievgen Zapolskyi 2019-01-16 09:22:42 UTC
Verified in manageiq/manageiq:hammer-1

Comment 5 errata-xmlrpc 2019-02-07 23:03:59 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://access.redhat.com/errata/RHSA-2019:0212


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