Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1593046

Summary: scp step missing in ceph admin guide -- adding a monitor section (CLI)
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Warren <wusui>
Component: DocumentationAssignee: Aron Gunn <agunn>
Status: CLOSED CURRENTRELEASE QA Contact: Tejas <tchandra>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.0CC: agunn, kdreyer, mmurthy
Target Milestone: z1   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-09 15:19:11 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: 1743515    

Description Warren 2018-06-20 00:17:11 UTC 
Description of problem:
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/administration_guide/#adding_a_monitor

In section 6.3:
steps 7 though 9 are not complete. Here's what I think is needed:

step 5 should say that the /tmp/ceph directory should be created on both the existing monitor and the new monitor node.

step 7 and step 8 should be performed on the existing monitor node

MISSING: In step 8.5 one should scp the keyring and monmap from the existing mon node to the node to be installed.

step 9. should be performed on the node that the new monitor will be installed on.

This may be figure-outable by many users but probably should be corrected.


Version-Release number of selected component (if applicable):
3.0
Comment 3 Giridhar Ramaraju 2019-08-05 13:07:09 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 4 Giridhar Ramaraju 2019-08-05 13:09:42 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 5 Giridhar Ramaraju 2019-08-20 07:17:24 UTC 
Level setting the severity of this defect to "High" with a bulk update. Pls
refine it to a more closure value, as defined by the severity definition in
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity