Description of problem: If you deploy a 4.5.0 appliance and then yum update it to 4.5.1 before you configure it, it appears that somewhere in the yum update process the v2_key gets created. If you then use ``appliance_console_cli`` to try to configure the appliance it errors out and tells you that it found the v2_key and to use the ``--force-key`` flag. Version-Release number of selected component (if applicable): 5.8.1 How reproducible: Always Steps to Reproduce: 1. Deploy 5.8.0 appliance 2. Update appliance to latest release (5.8.1) 3. run the following command: appliance_console_cli --key --internal --dbdisk=/dev/sdb --username=root --password=smartvm --dbname=vmdb_production --region=123 Actual results: appliance states that v2key already exists Expected results: configuration success of appliance Additional info: Found the same on appliance upgraded from 5.7.2 -> 5.7.3
Should be fixed by https://github.com/ManageIQ/manageiq-appliance/pull/123
The key that is generated is of no importance, if you need to join the appliance to a region then you can just remove it and fetch the other key. If you are creating the database using that key, that is also okay as the key was generated (not shipped with the rpm)
*** Bug 1395824 has been marked as a duplicate of this bug. ***
Verified in 5.9.0.1
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