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 1622997

Summary: Removing Monitors from an Unhealthy Cluster documentation need to be updated
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vikas Parashar <vparasha>
Component: DocumentationAssignee: Aron Gunn <agunn>
Status: CLOSED NOTABUG QA Contact: Tejas <tchandra>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.2CC: agunn, kdreyer
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: 2019-09-09 21:14: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: 1743515    

Description Vikas Parashar 2018-08-28 11:25:20 UTC
Description of problem:

Regarding "Administration Guide" of RHCS 3, I found a mistake in the content("6.2.3. Removing Monitors from an Unhealthy Cluster").
It cannot delete MON by following the procedure.
<https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/administration_guide/managing_cluster_size#removing_monitors_from_an_unhealthy_cluster>


Version-Release number of selected component (if applicable):
3.2

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

http://docs.ceph.com/docs/master/rados/operations/add-or-rm-mons/#removing-monitors-from-an-unhealthy-cluster


Additional info:

Comment 3 Giridhar Ramaraju 2019-08-05 13:08:25 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:54 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:13:13 UTC
evel 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