Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1684259 - Documentation for installing CFME 4.7 has the wrong option number.
Summary: Documentation for installing CFME 4.7 has the wrong option number.
Status: NEW
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.10.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.10.3
Assignee: Red Hat CloudForms Documentation
QA Contact: Red Hat CloudForms Documentation
Red Hat CloudForms Documentation
Depends On:
TreeView+ depends on / blocked
Reported: 2019-02-28 20:15 UTC by William Fitzgerald
Modified: 2019-03-01 15:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Category: ---
Cloudforms Team: Documentation
Target Upstream Version:

Attachments (Terms of Use)
Appliance console differences between 4.6 and 4.7 (deleted)
2019-02-28 20:17 UTC, William Fitzgerald
no flags Details

Description William Fitzgerald 2019-02-28 20:15:46 UTC
Document URL:

Section Number and Name: 
Installing_red_hat_cloudforms_on_vmware_vsphere 2.2.1
Describe the issue: 
There were 2 new options added to appliance console in 4.7 that change the selection from 5 to 7.
I included a screenshot of the appliance console from 4.6 and from 4.7.
See attachment

Suggestions for improvement: 

Additional information: 
Options 4 and 5 were added in 4.7 so all of the option numbers greater than 3 have been changed
All 4.7 documentation for appliance console should be verified. Any option number greater than 3 will be different in 4.7

Comment 2 William Fitzgerald 2019-02-28 20:17:25 UTC
Created attachment 1539622 [details]
Appliance console differences between 4.6 and 4.7

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