Bug 1568555 - 1.5. Migrating from CFME 5.7 to 5.8
Summary: 1.5. Migrating from CFME 5.7 to 5.8
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: GA
: cfme-future
Assignee: Red Hat CloudForms Documentation
QA Contact: Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-17 18:36 UTC by Paul Armstrong
Modified: 2019-12-19 15:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-19 15:46:24 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Paul Armstrong 2018-04-17 18:36:33 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.5/html/migrating_to_red_hat_cloudforms_4.5/index#migrate_appliances_42-45

Section Number and Name: 1.5. Migrating from CFME 5.7 to 5.8

Describe the issue: 
Steps do not indicate to user that any existing custom certificates are now replaced and saved as .rmpsave files 

e.g. 
/var/www/miq/vmdb/certs/server.cer.rpmsave
/var/www/miq/vmdb/certs/server.cer.key.rpmsave

For the chrome browser this will likely cause an invalid certificate error and an alternative name error.


Suggestions for improvement: 
Remind the user to check the certificates.

Additional information: 
I will attach a related BZ as the information for reconfiguring the httpd/conf.d/ applications files have also changed from cfme-blah-blah to manageiq

Comment 2 Dave Johnson 2018-04-17 18:44:24 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.


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