Bug 1462032

Summary: appliance_console asks for database password twice when connecting to remote database
Product: Red Hat CloudForms Management Engine Reporter: Jeffrey Cutter <jcutter>
Component: ApplianceAssignee: Gregg Tanzillo <gtanzill>
Status: CLOSED ERRATA QA Contact: luke couzens <lcouzens>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.8.0CC: abellott, jhardy, lcouzens, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: black
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:13:38 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:

Description Jeffrey Cutter 2017-06-15 23:27:41 UTC 
Description of problem:

At one point in time, when creating the vmdb database, the appliance_console only asked for the database password once.  This was bad as you could fat finger the password and not know it.  When that was fixed to verify the password, the connect to remote database also started asking for the password twice.  This is unnecessary as it will be self evident that the password is wrong when it cannot connect.

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

5.8.0

How reproducible:

Always

Steps to Reproduce:
1.  Join a new appliance to an existing database region.
2.  Note that it requests the database password twice, but only asks for password to get the keys once.

Additional info:

Database Configuration
Enter the database hostname or IP address: cfme02
Enter the port number: |5432| 
Enter the name of the database on cfme02: |vmdb_production| 
Enter the username: |root| 
Enter the database password on cfme02: *******
Enter the database password again: *******
Comment 2 CFME Bot 2017-06-23 21:28:42 UTC 
https://github.com/ManageIQ/manageiq-gems-pending/pull/214
Comment 3 luke couzens 2017-10-11 09:42:48 UTC 
Verified in 5.9.0.1
Comment 7 errata-xmlrpc 2018-03-01 13:13:38 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-2018:0380