Bug 1395824 - Re-evaluate process for generating v2_key files for new appliances
Summary: Re-evaluate process for generating v2_key files for new appliances
Keywords:
Status: CLOSED DUPLICATE of bug 1479859
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Nick Carboni
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-16 18:53 UTC by Gregg Tanzillo
Modified: 2017-12-05 15:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-18 14:20:18 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.