Bug 1383555

Summary: Upgrade process not clear on "bin/rake evm:automate:reset"
Product: Red Hat CloudForms Management Engine Reporter: Tsai Li Ming <ltsai>
Component: DocumentationAssignee: Red Hat CloudForms Documentation <cloudforms-docs>
Status: CLOSED WONTFIX QA Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: adahms, hhudgeon, jhardy, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: doc
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-08 23:34:20 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 Tsai Li Ming 2016-10-11 02:33:35 UTC 
Document URL: 
https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/general-configuration/#regions

Section Number and Name: 
4.1.1.5.2. Updating Appliances

Describe the issue: 
1. We should highlight this statement: "The appliance may be rebooted automatically during this process." Can this actually happen?

2. "Red Hat recommends updating the appliance using the Red Hat Updates tab only, which automatically restarts services and the appliance if needed. ". 

I updated from CF 4.1.1 to CF 4.1.2 using the UI "apply CFME update", and the default automation domain wasn't updated. I had to refer to the 4.0 -> 4.1 update guide to run `bin/rake evm:automate:reset`. Should we run this as part of the update process or highlight additional manual steps to the user in the UI?

3. Our errata (https://rhn.redhat.com/errata/RHSA-2016-1996.html) guide on applying the errta isn't correct. It points to a generic RHEL update. Can the instructions to apply the errata be specific to CF?
Comment 2 Andrew Dahms 2018-10-08 23:34:20 UTC 
Thank you for raising this bug.

We have evaluated this request, and while we recognize that it is a valid request for the documentation, we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. 

If you have any concerns about this, please feel free to contact Andrew Dahms.