Bug 2109362 - [doc] [administration guide] : Power off and on entire cluster : steps on Power off and power on needs changes
Summary: [doc] [administration guide] : Power off and on entire cluster : steps on Pow...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 5.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 6.1z1
Assignee: Akash Raj
QA Contact: Veera Raghava Reddy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-21 04:12 UTC by Vasishta
Modified: 2023-08-28 07:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-28 07:31:48 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-4869 0 None None None 2022-07-21 04:17:56 UTC

Description Vasishta 2022-07-21 04:12:26 UTC 
Describe the issue:
In section 2.6. Powering down and rebooting Red Hat Ceph Storage cluster

The steps given to power on and power off needs modification.

In sub-section - *Powering down the Red Hat Ceph Storage cluster-In section* - steps 5,6

In sub-section *Rebooting the Red Hat Ceph Storage cluster* - 
steps 2,3

Currently it appears like we have provided examples to power off or on the nodes. Where as the example is for stop the respective services only.

We need to say that the example is only for stopping the service and each OSD in osd node and it needs to be repeated on each OSD node.
Refer solutions/2139301 Private Notes section.

Describe the task you were trying to accomplish:
Pwer off and on the cluster

Suggestions for improvement:
Mentioned above

Chapter/Section Number and Title:
Mentioned above 

Product Version:
5.x

Environment Details:
_NA_

Any other versions of this document that also needs this update:
No as solutions/2139301 seems to be addressing.

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