Bug 1367622

3.a. Should probably talk about how you can have all the passwords set to the same thing by setting the password values.

3.b.   Do we want to talk about the options that appear if you select "After manually publishing them".   I've never really understood them, so I'm assuming there will be others who don't.

4.  I would change this:

The advantage of self-hosted engine is that with two self-hosted engine hosts configured, the Manager can be highly available. 

To what is in the docs for RHV (https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/self-hosted-engine-guide/chapter-1-introduction):

The advantage of choosing self-hosted engine with two or more hypervisors is that, if the host running the Manager virtual machine goes into maintenance mode, or fails unexpectedly, the virtual machine will be migrated automatically to another host in the environment.

4.c.   We should probably document the Edit Naming Scheme screen.

4.e.  No need to say "Ensure there are no trailing spaces in the share path." the UI checks for this now.

5.   We should mention selecting the openshift sample application.

(In reply to James Olin Oden from comment #3)
Hi James,
   Thanks for your feedback!

3a- I personally think enough information is provided in the UI, and it is called a 'universal password'.

3b- Updated the step to:
-----
 Select Immediately to publish updates immediately when an update is available. Click Next. Alternatively, select After manually publishing them, click New Environment Path, and enter an environment name. The Label is used as an internal ID and is identical to the environment name. Optionally enter a description, and click Submit. Click Next.

Note
If you select Immediately, the content view for the deployment is in the default Library environment, and updates will be available to the deployment as soon as they are released. If you would like more control on when a deployment can receive updates, you need to select After manually publishing them, and create a new environment path (for example: Library > Production). This way, you will be able to promote the content from the default Library environment to a Production environment manually. For more information, see Creating an Application Life Cycle in the Red Hat Satellite Content Management Guide. 
-----

4- Sure. Updated.

4c- I actually think the options are quite self-explanatory, and that's why I filed https://bugzilla.redhat.com/show_bug.cgi?id=1339808#c1 so there is enough information in the UI for users to know which option to use. Please let me know if you feel anything might be confusing for users still. It is more a preference thing than something required for the procedure.

4e- I believe it was once fixed and then a regression bug, but yep, I've removed the note for GA.

5- The mentioning of the sample app is in 5f already:
---
Set a subdomain name, and optionally select to deploy a sample application as part of the deployment. The subdomain name appears as part of the application URL. 
---

Thom, I believe you are the Satellite expert. Could you have a look at the change for step3b please?

Many thanks,
Julie

Julie, other than it is Red Hat Satellite 6 Content Management Guide, that sounds right to me

Based on https://bugzilla.redhat.com/show_bug.cgi?id=1367622#c4, moving to VERIFIED

Just wanted to look at the changes requested or comments on the reason why there was no change, before setting to verify.

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://access.redhat.com/errata/RHEA-2016:1862