Hi Erin,

As discussed, the changes are not yet reflecting in all the required sections. Please move the BZ back to ON_QA once all requested changes for oc logs command in [1] 
 are also added 

[1] https://docs.google.com/document/d/1Guc7SsTiGik_-QmfeR0AVI6O-Je81lBFSgzATU1z2eY/edit#

Thanks Erin for the changes.

Confirmed that all instances(5 in total) of `# oc logs -l job-name=ocs-osd-removal-${osd_id_to_remove}` along with the e.g. of log output has been replaced with following message/step:


Verify that the OSD is removed successfully by checking the status of the ocs-osd-removal pod. A status of Completed confirms that the OSD removal job succeeded.

# oc get pod -l job-name=ocs-osd-removal-${osd_id_to_remove} -n openshift-storage
NOTE
If ocs-osd-removal fails and the pod is not in the expected Completed state, check the pod logs for further debugging. For example:

# oc logs ${osd_id_to_remove} -n openshift-storage --tail=-1

Based on this, moving the BZ to verified state.


Changes reflected here

8.3.1. Replacing failed storage nodes on bare metal infrastructure (step 16)
8.3.2. Replacing failed storage nodes on Amazon EC2 infrastructure (Step 10. vi)
8.3.3. Replacing failed storage nodes on VMware infrastructure (Step 16)
9.2.1. Replacing operational or failed storage devices on VMware user-provisioned infrastructure (Step 5)
9.3.2. Replacing operational or failed storage devices on VMware and bare metal infrastructures (Step 5)

HI Erin

@akarsha pointed out that the following command doesnt work. And it is true as we are not using the pod name properly

 oc logs ${osd_id_to_remove} -n openshift-storage --tail=-1

We might need this to be changed in 5 places. Sorry for missing out and verifying the BZ with incorrect command

$ oc logs -l job-name=ocs-osd-removal-${osd_id_to_remove} -n openshift-storage --tail=-1