Bug 1479859

Summary: yum update from cloudforms 4.5.0 to 4.5.1 creates v2_key
Product: Red Hat CloudForms Management Engine Reporter: Ryan Spagnola <rspagnol>
Component: ApplianceAssignee: Nick Carboni <ncarboni>
Status: CLOSED ERRATA QA Contact: luke couzens <lcouzens>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8.0CC: abellott, gtanzill, jhardy, lcouzens, ncarboni, obarenbo, simaishi, smallamp
Target Milestone: GA   
Target Release: 5.9.0   
Hardware: All   
OS: All   
Whiteboard: upgrade: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:15:53 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 Ryan Spagnola 2017-08-09 15:05:11 UTC 
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
Comment 2 Nick Carboni 2017-09-18 14:13:30 UTC 
Should be fixed by https://github.com/ManageIQ/manageiq-appliance/pull/123
Comment 3 Nick Carboni 2017-09-18 14:14:52 UTC 
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)
Comment 4 Nick Carboni 2017-09-18 14:20:18 UTC 
*** Bug 1395824 has been marked as a duplicate of this bug. ***
Comment 5 luke couzens 2017-10-11 12:25:32 UTC 
Verified in 5.9.0.1
Comment 8 errata-xmlrpc 2018-03-01 13:15:53 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