Bug 1395824

Summary: Re-evaluate process for generating v2_key files for new appliances
Product: Red Hat CloudForms Management Engine Reporter: Gregg Tanzillo <gtanzill>
Component: ApplianceAssignee: Nick Carboni <ncarboni>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.7.0CC: abellott, jhardy, ncarboni, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-18 14:20:18 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:

Description Gregg Tanzillo 2016-11-16 18:53:08 UTC 
Description of problem:

As a followup to BZ https://bugzilla.redhat.com/show_bug.cgi?id=1395379, we should re-evaluate this process. 

I the referenced BZ, the customer deployed new appliances, applied a patch and started up the appliance before either creating or copying the correct v2_key. By doing this, a new v2_key was created that was not valid for the existing DB. Also, there was no option in the appliance console menu to copy one from another appliance because of the existing one.

This prevented the appliance form starting because the encryption key was not valid.
Comment 2 Nick Carboni 2017-09-18 14:20:18 UTC 
Closing this as applying patches an upgrading should no longer generate a v2_key. See bug 1479859 for details.

*** This bug has been marked as a duplicate of bug 1479859 ***