Description of problem:
Change "5.2. REMOVING A HOST FROM A SELF-HOSTED ENGINE ENVIRONMENT" section, as undeployment should be made differently than described in the chapter.

It is incorrectly described in section 5.2: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/self-hosted_engine_guide/removing_a_host_from_a_self-hosted_engine_environment

Version-Release number of selected component (if applicable):
ovirt-vmconsole-1.0.4-1.el7ev.noarch
qemu-kvm-rhev-2.6.0-28.el7_3.9.x86_64
ovirt-imageio-daemon-1.0.0-0.el7ev.noarch
ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch
sanlock-3.4.0-1.el7.x86_64
ovirt-vmconsole-host-1.0.4-1.el7ev.noarch
mom-0.5.9-1.el7ev.noarch
vdsm-4.19.15-1.el7ev.x86_64
ovirt-hosted-engine-ha-2.1.0.6-1.el7ev.noarch
ovirt-setup-lib-1.1.0-1.el7ev.noarch
ovirt-imageio-common-1.0.0-0.el7ev.noarch
libvirt-client-2.0.0-10.el7_3.5.x86_64
ovirt-hosted-engine-setup-2.1.0.6-1.el7ev.noarch
ovirt-host-deploy-1.6.5-1.el7ev.noarch
Linux version 3.10.0-514.21.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Apr 22 02:41:35 EDT 2017
Linux 3.10.0-514.21.1.el7.x86_64 #1 SMP Sat Apr 22 02:41:35 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.3 (Maipo)


How reproducible:
100%

Steps to Reproduce:
1.In order to undeploy ha-host you should got to Hosts tab.
2.Select ha-host and set it in to maintenance.
3.Click on installation tab.
4.Select "Reinstall" option from drop-down menu.
5.Select Hosted Engine tab.
6.Choose hosted engine deployment action UNDEPLOY.
7.Confirm by pressing "OK" button.

Actual results:
In currently described section 5.2, customer won't find Hosted Engine tab, after he/she will "edit" ha-host under maintenance as it was removed from there.

Expected results:
Change to reproduction steps as appears above.

Additional info:
This bug being created forth to https://bugzilla.redhat.com/show_bug.cgi?id=1442580.

"> 2) Is this documented somewhere in downstream documentation?

I haven't found if it is in the documentation somewhere.
It was introduced in this RFE: Bug 1167262 .

> 3)Proposed new way of undeployment e.g. maintenance the host, reinstall,
> hosted engine, undeploy, did worked, although metadata was not cleaned
> properly from shared storage, and I still could see already undeployed
> alma04, in CLI, from alma03:"