Bug 2196936 - Correct method for removing entire OSD disk from OSD Host
Summary: Correct method for removing entire OSD disk from OSD Host
Keywords:
Status: RELEASE_PENDING
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 5.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 6.1z1
Assignee: Akash Raj
QA Contact: Aditya Ramteke
Anjana Suparna Sriram
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-10 20:44 UTC by Scott Nipp
Modified: 2023-07-17 18:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6641 0 None None None 2023-05-10 20:44:57 UTC

Description Scott Nipp 2023-05-10 20:44:20 UTC
Describe the issue:  Correct method for removing entire OSD disk from OSD Host

Describe the task you were trying to accomplish:  Customer was following section 6.10 to remove an OSD drive.  After completing the documented process the OSD node was rebooted and the removed OSD drive was rebuilt on the node.

Suggestions for improvement:  There is a Note in section 6.11 for replacing OSDs that specifically covers this exact issue.  Copying this Note up to section 6.10 would help to avoid this confusion going forward.

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/5/html-single/operations_guide/index#removing-the-osd-daemons-using-the-ceph-orchestrator_ops
Chapter/Section Number and Title:
6.10. Removing the OSD daemons using the Ceph Orchestrator
Product Version:
  Specifically this customer is running Ceph 5.3.
Environment Details:

Any other versions of this document that also needs this update:

Additional information:
An additional step or note might be that the physical drive or virtual device should be removed or unallocated to the node after the OSD is removed via the documented process.


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