Merge pull request #66783 from apinnick/update-runbook-3

update VirtualMachineCRCErrors runbook

Author: apinnick

modules/virt-runbook-virtualmachinecrcerrors.adoc

@@ -27,41 +27,45 @@ severe performance degradation.
 [id="diagnosis-virtualmachinecrcerrors"]
 == Diagnosis
 
-. Get the volume name from a virtual machine:
+. Navigate to *Observe* -> *Metrics* in the web console.
+. Obtain a list of virtual machines with incorrectly configured storage classes
+by running the following PromQL query:
 +
-[source,terminal]
+[source,text]
 ----
-$ oc get vm <vm_name> -o jsonpath='{.spec.template.spec.volumes}'
+kubevirt_ssp_vm_rbd_volume{rxbounce_enabled="false", volume_mode="Block"} == 1
 ----
-
-. Get the storage class name from the volume:
 +
-[source,terminal]
+The output displays a list of virtual machines that use a storage
+class without `rxbounce_enabled`.
++
+.Example output
++
+[source,text]
 ----
-$ oc get pvc <volume> -o jsonpath='{.spec.storageClassName}'
+kubevirt_ssp_vm_rbd_volume{name="testvmi-gwgdqp22k7", namespace="test_ns", pv_name="testvmi-gwgdqp22k7", rxbounce_enabled="false", volume_mode="Block"} 1
 ----
 
-. Get the storage class configuration:
+. Obtain the storage class name by running the following command:
 +
 [source,terminal]
 ----
-$ oc get sc <storage_class> -o yaml
+$ oc get pv <pv_name> -o=jsonpath='{.spec.storageClassName}'
 ----
 
-. Check the storage class configuration for the `krbd:rxbounce` map option.
-
 [discrete]
 [id="mitigation-virtualmachinecrcerrors"]
 == Mitigation
 
-Add the `krbd:rxbounce` map option to the storage class configuration:
+Add the `krbd:rxbounce` map option to the storage class configuration to use
+a bounce buffer when receiving data:
 
-[source,terminal]
+[source,yaml]
 ----
 apiVersion: storage.k8s.io/v1
 kind: StorageClass
 metadata:
-  name: example-storage-class
+  name: vm-sc
 parameters:
   # ...
   mounter: rbd
@@ -72,7 +76,7 @@ provisioner: openshift-storage.rbd.csi.ceph.com
 
 The `krbd:rxbounce` option creates a bounce buffer to receive data. The default
 behavior is for the destination buffer to receive data directly. A bounce buffer
-is required if the destination buffer is unstable.
+is required if the stability of the destination buffer cannot be guaranteed.
 
 If you cannot resolve the issue, log in to the
 link:https://access.redhat.com[Customer Portal] and open a support case,