Bug 1200424 - When migrating to CloudForms 5.3.1 getting 'no encryption key v0_key'
Summary: When migrating to CloudForms 5.3.1 getting 'no encryption key v0_key'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.4.0
Assignee: Joe Vlcek
QA Contact: Jan Krocil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-10 14:22 UTC by Jared Deubel
Modified: 2019-04-16 14:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-16 12:52:05 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1100 0 normal SHIPPED_LIVE CFME 5.4.0 bug fixes, and enhancement update 2015-06-16 16:28:42 UTC

Comment 3 Jared Deubel 2015-03-10 15:24:35 UTC
Created attachment 1000012 [details]
database.yml

Comment 13 CFME Bot 2015-04-06 21:05:59 UTC
New commit detected on manageiq/master:
https://github.com/ManageIQ/manageiq/commit/98e764141b7a43143dd1b83a97a0e2342ee989e3

commit 98e764141b7a43143dd1b83a97a0e2342ee989e3
Author:     Keenan Brock <kbrock>
AuthorDate: Tue Mar 31 11:09:44 2015 -0400
Commit:     Keenan Brock <kbrock>
CommitDate: Mon Apr 6 11:34:22 2015 -0400

    MiqPassword: Don't auto load legacy keys (v0/v1)
    
    This gives us an easier way to migrate appliances
    to use newer keys
    
    fix_auth still does load these keys
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1200424

 lib/spec/util/miq-password_spec.rb | 24 ++++++++++++++----------
 lib/util/miq-password.rb           | 28 ++++++++++++++++------------
 vmdb/tools/fix_auth/fix_auth.rb    |  8 +++++++-
 3 files changed, 37 insertions(+), 23 deletions(-)

Comment 23 errata-xmlrpc 2015-06-16 12:52:05 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://rhn.redhat.com/errata/RHBA-2015-1100.html


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