Bug 1485911

Summary: Removing a Host procedure needs to be changed
Product: Red Hat Satellite Reporter: Harshad More <hmore>
Component: Docs Host Configuration GuideAssignee: Stephen Wadeley <swadeley>
Status: CLOSED CURRENTRELEASE QA Contact: Melanie Corr <mcorr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.10CC: hmore, swadeley
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-08 07:36:14 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:
Embargoed:

Description Harshad More 2017-08-28 12:22:55 UTC
Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html-single/host_configuration_guide/#sect-Red_Hat_Satellite-Host_Configuration_Guide-Configuring_Hosts-Removing_a_Host

Section Number and Name: 
10.12. REMOVING A HOST

Describe the issue: 

Procedure 10.18. To Disassociate A Virtual Machine from Satellite without Removing it from a Hypervisor

Steps given under this are not correct. Since current satellite version 6.2.11 don't have the button named "Disassociate VMs" under virtual machine which reflects under compute resource as guided in the document.

Even in future if it comes then procedure mentioned would disassociate ALL VMs

Suggestions for improvement: 

To disassociate a single host, go to Hosts --> All hosts, choose your host, select Edit and
then the Disassociate host button in the upper right corner.


Additional information: 

Steps should same as mentioned in article https://access.redhat.com/solutions/1504603

Comment 1 Stephen Wadeley 2017-08-28 12:50:43 UTC
Hello Harshad

Thank you for raising this bug. I was just investigating this procedure and the Disassociate button. Translators mentioned they could not see the button. Thanks for the link; now I see its not my configuration that was the problem.