Merge pull request #63536 from apinnick/CNV-32025

CNV- 32025: Update CDIDataVolumeUnusualRestartCount

Author: apinnick

modules/virt-runbook-cdidatavolumeunusualrestartcount.adoc

@@ -12,37 +12,26 @@
 [id="meaning-cdidatavolumeunusualrestartcount"]
 == Meaning
 
-This alert fires when a `DataVolume` object restarts more than three
-times.
+This alert fires when a `DataVolume` object restarts more than three times.
 
 [discrete]
 [id="impact-cdidatavolumeunusualrestartcount"]
 == Impact
 
-Data volumes are responsible for importing and creating a virtual
-machine disk on a persistent volume claim. If a data volume restarts
-more than three times, these operations are unlikely to succeed. You
-must diagnose and resolve the issue.
+Data volumes are responsible for importing and creating a virtual machine disk
+on a persistent volume claim. If a data volume restarts more than three times,
+these operations are unlikely to succeed. You must diagnose and resolve the issue.
 
 [discrete]
 [id="diagnosis-cdidatavolumeunusualrestartcount"]
 == Diagnosis
 
-. Obtain the name and namespace of the data volume:
+. Find Containerized Data Importer (CDI) pods with more than three restarts:
 +
 [source,terminal]
 ----
-$ oc get dv -A -o json | jq -r '.items[] | \
-  select(.status.restartCount>3)' | jq '.metadata.name, .metadata.namespace'
-----
-
-. Check the status of the pods associated with the data volume:
-+
-[source,terminal]
-----
-$ oc get pods -n <namespace> -o json | jq -r '.items[] | \
-  select(.metadata.ownerReferences[] | \
-  select(.name=="<dv_name>")).metadata.name'
+$ oc get pods --all-namespaces -l app=containerized-data-importer \
+  -o=jsonpath='{range .items[?(@.status.containerStatuses[0].restartCount>3)]}{.metadata.name}{"/"}{.metadata.namespace}{"\n"}'
 ----
 
 . Obtain the details of the pods:
@@ -56,7 +45,7 @@ $ oc -n <namespace> describe pods <pod>
 +
 [source,terminal]
 ----
-$ oc -n <namespace> describe logs <pod>
+$ oc -n <namespace> logs <pod>
 ----
 
 [discrete]
@@ -65,6 +54,6 @@ $ oc -n <namespace> describe logs <pod>
 
 Delete the data volume, resolve the issue, and create a new data volume.
 
-If you cannot resolve the issue, log in to the link:https://access.redhat.com[Customer
-Portal] and open a support case,
-attaching the artifacts gathered during the diagnosis procedure.
+If you cannot resolve the issue, log in to the
+link:https://access.redhat.com[Customer Portal] and open a support case,
+attaching the artifacts gathered during the Diagnosis procedure.