Bug 1462032 - appliance_console asks for database password twice when connecting to remote database
appliance_console asks for database password twice when connecting to remote ...
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: GA
: 5.9.0
Assigned To: Gregg Tanzillo
luke couzens
Depends On:
  Show dependency treegraph
Reported: 2017-06-15 19:27 EDT by Jeffrey Cutter
Modified: 2018-03-01 08:13 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-03-01 08:13:38 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeffrey Cutter 2017-06-15 19:27:41 EDT
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):


How reproducible:


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 3 luke couzens 2017-10-11 05:42:48 EDT
Verified in
Comment 7 errata-xmlrpc 2018-03-01 08:13:38 EST
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.


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