Bug 1761390

Summary: [GSS][DOC] RHHI node replacement steps should not configure RHGS using web console
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: MAYANK PANDEY <mpandey>
Component: doc-Maintaining_RHHIAssignee: Laura Bailey <lbailey>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhhiv-1.6CC: asriram, lbailey, rhs-bugs, sabose, sasundar
Target Milestone: ---   
Target Release: RHHI-V 1.7.z Async Update   
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: 2020-02-26 08:05:54 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:
Bug Depends On:    
Bug Blocks: 1804071    

Description MAYANK PANDEY 2019-10-14 10:26:44 UTC 
Document URL: 

RHHI 1.6 Administration Document
https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.6/html-single/maintaining_red_hat_hyperconverged_infrastructure_for_virtualization/index

Section Number and Name: 

13. Replacing hosts
https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.6/html-single/maintaining_red_hat_hyperconverged_infrastructure_for_virtualization/index#replacing-hosts


Describe the issue: 


In RHHI administration document, the node replacement section deals with replacing a failed node. We can either use the same FQDN or configure a new one for replacement. The steps to perform the replacement are:

Install the replacement host:

https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.6/html-single/maintaining_red_hat_hyperconverged_infrastructure_for_virtualization/index#task-replace-primary-hc-host-using-ansible

Follow the instructions in Deploying Red Hat Hyperconverged Infrastructure for Virtualization for Virtualization to install the physical machine and configure storage on the new host.

    Installing hyperconverged hosts
    Configuring Public Key based SSH Authentication
    Configuring RHGS for Hosted Engine using the Web Console  <===

The above-highlighted step creates a new RHHI cluster. So not sure if that should be part of the replacement process. Same can be seen in the Replacing a hyperconverged host to use the same FQDN


https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.6/html-single/maintaining_red_hat_hyperconverged_infrastructure_for_virtualization/index#replacing_hc_host_same_fqdn


13.3. Preparing a replacement hyperconverged host using ansible

Follow this process to replace a hyperconverged host in the cluster.

Prerequisites

    Ensure that the host you intend to replace is not associated with the FQDN that you want to use for the new host.
    Ensure that the new host is associated with the FQDN you want it to use. 

The above two sentences are confusing as we are to prepare a host with the same FQDN. In case we just want to reinstall a hos which is already part of the RHHI cluster, it would have the same FQDN


Suggestions for improvement: 

Please test the end to end process for host replacement for primary as well as other hosts and clarify with detailed steps on what needs to be done and what is automated under the host preparation.


Additional information: