Bug 1639547 - Minor bug in section on replacing a host with same hostname
Summary: Minor bug in section on replacing a host with same hostname
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Administration_Guide
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.4.z Async Update
Assignee: Anjana KD
QA Contact: Vinayak Papnoi
URL:
Whiteboard:
Depends On:
Blocks: 1660873
TreeView+ depends on / blocked
 
Reported: 2018-10-16 04:52 UTC by Krutika Dhananjay
Modified: 2019-02-08 18:37 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-08 18:37:05 UTC
Embargoed:


Attachments (Terms of Use)

Description Krutika Dhananjay 2018-10-16 04:52:18 UTC
Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html/administration_guide/sect-replacing_hosts

Section Number and Name: 

11.10.2. Replacing a Host Machine with the Same Hostname

Describe the issue: 

I was following the steps in section 11.10.2 to replace a host with same hostname and I think that point #11 needs a minor change in that the following sentence

"Copy the peer file corresponding to the UUID of the host retrieved in Step 4 to the new host (server0.example.com) by executing the following command:

# scp /var/lib/glusterd/peers/<UUID-retrieved-from-step4> root@Example1:/var/lib/glusterd/peers/"

should be referring to Step 5 as opposed to Step 4 both in the English description and the example command.

It should instead read:

"Copy the peer file corresponding to the UUID of the host retrieved in Step 5 to the new host (server0.example.com) by executing the following command:

# scp /var/lib/glusterd/peers/<UUID-retrieved-from-step5> root@Example1:/var/lib/glusterd/peers/"


Suggestions for improvement: 

Additional information:

Comment 2 Krutika Dhananjay 2018-10-16 04:55:24 UTC
Atin,

Could you confirm that this is indeed a bug? These steps are concerned with importing glusterd peer information. So it's best to also hear it straight from the horse's mouth.

Thanks,
Krutika

Comment 3 Atin Mukherjee 2018-10-28 15:55:30 UTC
(In reply to Krutika Dhananjay from comment #2)
> Atin,
> 
> Could you confirm that this is indeed a bug? These steps are concerned with
> importing glusterd peer information. So it's best to also hear it straight
> from the horse's mouth.

Bingo, you're right! I believe this has happened due to some steps changing resulting in numbering of the steps to change as well.


> 
> Thanks,
> Krutika

Comment 6 Anjana KD 2019-01-14 11:19:04 UTC
 preview link: https://access.qa.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html-single/administration_guide/#Replacing_a_Host_Machine_with_the_Same_Hostname

I have made the required changes in step 11 in section 11.10.2  
Kindly verify.

Comment 7 Vinayak Papnoi 2019-01-14 11:45:36 UTC
(In reply to Anjana from comment #6)
>  preview link:
> https://access.qa.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/
> html-single/administration_guide/
> #Replacing_a_Host_Machine_with_the_Same_Hostname
> 
> I have made the required changes in step 11 in section 11.10.2  
> Kindly verify.

Step 11 of section 11.10.2 in the link provided reflects the changes mentioned in the description.

Moving the bug to VERIFIED.


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