Merge pull request #84711 from snarayan-redhat/OSDOCS-11332_removesteps

OSDOCS#11332: Removed unnecessary steps for vSphere Problem Detector Operator check

Author: snarayan-redhat

modules/vsphere-problem-detector-running.adoc

@@ -18,41 +18,31 @@ The {operator-name} automatically runs the checks every hour. However, when the
 
 .Procedure
 
-. Scale the Operator to `0`:
+* Scale the Operator to `0`:
 +
 [source,terminal]
 ----
 $ oc scale deployment/vsphere-problem-detector-operator --replicas=0 \
     -n openshift-cluster-storage-operator
 ----
-+
-If the deployment does not scale to zero immediately, you can run the following command to wait for the pods to exit:
-+
-[source,terminal]
-----
-$ oc wait pods -l name=vsphere-problem-detector-operator \
-    --for=delete --timeout=5m -n openshift-cluster-storage-operator
-----
 
-. Scale the Operator back to `1`:
+.Verification
+
+* Verify that the pods have restarted by running the following command:
 +
 [source,terminal]
 ----
-$ oc scale deployment/vsphere-problem-detector-operator --replicas=1 \
-    -n openshift-cluster-storage-operator
+$ oc -n openshift-cluster-storage-operator get pod -l name=vsphere-problem-detector-operator -w
 ----
-
-. Delete the old leader lock to speed up the new leader election for the Cluster Storage Operator:
 +
+.Example output
 [source,terminal]
 ----
-$ oc delete -n openshift-cluster-storage-operator \
-    cm vsphere-problem-detector-lock
+NAME                                                 READY   STATUS    RESTARTS   AGE
+vsphere-problem-detector-operator-77486bd645-9ntpb   1/1     Running   0          11s
 ----
-
-.Verification
-
-* View the events or logs that are generated by the {operator-name}. Confirm that the events or logs have recent timestamps.
++
+The `AGE` field must indicate that the pod is restarted.
 
 // Clear temporary attributes
 :!operator-name: