Bug 1950979 - The command of creating debug pod on a node should be fixed
Summary: The command of creating debug pod on a node should be fixed
Keywords:
Status: CLOSED DUPLICATE of bug 1932224
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: documentation
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Anjana Suparna Sriram
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-19 10:21 UTC by Itzhak
Modified: 2021-04-19 11:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-19 11:36:56 UTC
Embargoed:


Attachments (Terms of Use)

Description Itzhak 2021-04-19 10:21:32 UTC
Describe the issue:
I noticed that in the documents of node replacement and device replacement, there is a little mistake in the command of creating a debug pod on a node: 
The command "oc debug node <node name>" should be replaced with "oc debug node/<node name>"

Describe the task you were trying to accomplish:
I tried to create a debug pod on the storage node to check something in the storage node.

Suggestions for improvement:
Change all occurrences of "oc debug node <node name>" to 
"oc debug node/<node name>"

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.6/html-single/replacing_nodes/index?lb_target=stage, https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.6/html-single/replacing_devices/index?lb_target=preview

Chapter/Section Number and Title:
All the sections in the docs have one occurrence with the error above. 

Product Version:
OCS 4.6

Environment Details:

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

Additional information:
We should check other documents as well to see if we didn't have the same problem

Comment 2 Olive Lakra 2021-04-19 11:36:56 UTC

*** This bug has been marked as a duplicate of bug 1932224 ***


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