Repository: openshift/runbooks
Pull request #231: Update openshift-virtualization-operator runbook
Author: login: c-monaa
Labels: name: ok-to-test
description: Indicates a non-member PR verified by an org member that is safe to test.
name: approved
description: Indicates a PR has been approved by an approver from all required OWNERS files.
name: lgtm
description: Indicates that a PR is ready to be merged.
Created: 2025-01-20T15:44:23Z | Merged: 2025-03-25T14:11:07Z

### Fix Incorrect Commands in Diagnosis Section of Runbooks in Monitoring doc

This PR modifies several commands in the Diagnosis section of the runbooks under the Monitoring section. The current commands contain errors or deprecated syntax, leading to issues when troubleshooting. Below are the necessary modifications:

**Modifications:**

1. CDIStorageProfilesIncomplete
* Current: Identify the incomplete storage profile using: oc get storageprofile <storage_class>
* Issue: This command only shows the storage profile associated with the given storage class but does not provide details on incompleteness. To identify incomplete ones, use: oc get storageprofile -o json | jq '.items[] | select(.status.claimPropertySets == null or .status.claimPropertySets == []) | .metadata.name'

2. KubeVirtVMIExcessiveMigrations
* Current: 
    * oc get nodes -l node-role.kubernetes.io/worker= -o json | jq .items[].status.allocatable
    * oc get nodes -l node-role.kubernetes.io/worker= -o json | jq .items[].status.conditions
* Issue: The commands fail due to missing single quotes. The correct versions are: 
    * oc get nodes -l node-role.kubernetes.io/worker= -o json | jq '.items[].status.allocatable'
    * oc get nodes -l node-role.kubernetes.io/worker= -o json | jq '.items[].status.conditions'

3. Runbooks: LowReadyVirtControllersCount, LowReadyVirtOperatorsCount, VirtAPIDown, etc.
* Issue: The namespace is exported incorrectly, causing errors due to the presence of “\n” along namespace.
* Fix: 
* export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace | tr -d '\n')"
											OR
*  export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace | xargs)"

4. LowVirtControllersCount
* Current: 
    * oc -n $NAMESPACE logs <virt-launcher>
    * oc -n $NAMESPACE describe pod/<virt-launcher>
* Issue: It should refer to virt-controller instead: 
    * oc -n $NAMESPACE logs <virt-controller>
    * oc -n $NAMESPACE describe pod/<virt-controller>

5. NetworkAddonsConfigNotReady
* Current: oc get networkaddonsconfig -o custom-columns="":.status.conditions[*].message
* Issue: The commands fail due to missing single quotes in custom column formatting. The correct versions is: oc get networkaddonsconfig -o custom-columns=':.status.conditions[*].message'

* Current: oc -n cluster-network-addons get daemonset <pod> -o yaml
* Issue: Incorrect resource type in daemonset retrieval. The correct versions is: oc -n cluster-network-addons get daemonset <demonset> -o yaml

* Current: oc -n cluster-network-addons describe <pod>
* Issue: Incomplete syntax in describe command. The correct command is: oc -n cluster-network-addons describe pod <pod>

6. NoLeadingVirtOperator
* Current: oc -n $NAMESPACE logs | grep lead
* Issue: The command is incomplete. It should specify virt-operator: oc -n $NAMESPACE logs <virt-operator> | grep lead

7. NoReadyVirtController
* Current: get pods -n $NAMESPACE | grep virt-controller
* Issue: Missing oc prefix. The correct command is: oc get pods -n $NAMESPACE | grep virt-controller

8. OrphanedVirtualMachineInstances
* Current: oc get daemonset virt-handler --all-namespaces
* Issue: The command fails due to resource retrieval restrictions. The corrected version is: oc get daemonsets --all-namespaces | grep virt-handler

* Current: oc get daemonset virt-handler --all-namespaces -o yaml | jq .status
* Issue: The command fails because the virt-handler DaemonSet may exist in multiple namespaces, and oc get daemonset <name> does not support --all-namespaces. The correct version is: oc get daemonsets --all-namespaces -o json | jq '.items[] | select(.metadata.name=="virt-handler") | .status'

* Current: oc get kubevirt kubevirt --all-namespaces -o yaml
* Issue: The command fails due to namespace retrieval issues. The correct version is: oc get kubevirt -n <namespace> <KubeVirt-name> -o yaml

9. VirtApiRESTErrorsBurst, VirtApiRESTErrorsHigh
* Current: oc describe -n $NAMESPACE <virt-api>
* Issue: Missing pod keyword. The corrected command is: oc describe pod -n $NAMESPACE <virt-api>





Diff:
diff --git a/alerts/openshift-virtualization-operator/CDIStorageProfilesIncomplete.md b/alerts/openshift-virtualization-operator/CDIStorageProfilesIncomplete.md
index 922f1961..2bf8b966 100644
--- a/alerts/openshift-virtualization-operator/CDIStorageProfilesIncomplete.md
+++ b/alerts/openshift-virtualization-operator/CDIStorageProfilesIncomplete.md
@@ -18,7 +18,7 @@ The CDI cannot create a VM disk on the PVC.
 - Identify the incomplete storage profile:
 
   ```bash
-  $ oc get storageprofile <storage_class>
+  $ oc get storageprofile -o json | jq '.items[] | select(.status.claimPropertySets == null or .status.claimPropertySets == []) | .metadata.name'
   ```
 
 ## Mitigation
diff --git a/alerts/openshift-virtualization-operator/KubeVirtVMIExcessiveMigrations.md b/alerts/openshift-virtualization-operator/KubeVirtVMIExcessiveMigrations.md
index 9e79f341..e934d236 100644
--- a/alerts/openshift-virtualization-operator/KubeVirtVMIExcessiveMigrations.md
+++ b/alerts/openshift-virtualization-operator/KubeVirtVMIExcessiveMigrations.md
@@ -19,7 +19,7 @@ performance because memory page faults occur during the transition.
 1. Verify that the worker node has sufficient resources:
 
    ```bash
-   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq .items[].status.allocatable
+   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq '.items[].status.allocatable'
    ```
 
    Example output:
@@ -42,7 +42,7 @@ performance because memory page faults occur during the transition.
 2. Check the status of the worker node:
 
    ```bash
-   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq .items[].status.conditions
+   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq '.items[].status.conditions'
    ```
 
    Example output:
diff --git a/alerts/openshift-virtualization-operator/LowReadyVirtControllersCount.md b/alerts/openshift-virtualization-operator/LowReadyVirtControllersCount.md
index c76a6c34..a3bf7b52 100644
--- a/alerts/openshift-virtualization-operator/LowReadyVirtControllersCount.md
+++ b/alerts/openshift-virtualization-operator/LowReadyVirtControllersCount.md
@@ -21,7 +21,7 @@ launching a new VMI or shutting down an existing VMI.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Verify a `virt-controller` device is available:
diff --git a/alerts/openshift-virtualization-operator/LowReadyVirtOperatorsCount.md b/alerts/openshift-virtualization-operator/LowReadyVirtOperatorsCount.md
index 28e7b276..0e444b19 100644
--- a/alerts/openshift-virtualization-operator/LowReadyVirtOperatorsCount.md
+++ b/alerts/openshift-virtualization-operator/LowReadyVirtOperatorsCount.md
@@ -32,7 +32,7 @@ affect VM workloads.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Obtain the name of the `virt-operator` deployment:
diff --git a/alerts/openshift-virtualization-operator/LowVirtAPICount.md b/alerts/openshift-virtualization-operator/LowVirtAPICount.md
index 53591ea4..8078ec19 100644
--- a/alerts/openshift-virtualization-operator/LowVirtAPICount.md
+++ b/alerts/openshift-virtualization-operator/LowVirtAPICount.md
@@ -15,7 +15,7 @@ becomes a single point of failure.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the number of available `virt-api` pods:
diff --git a/alerts/openshift-virtualization-operator/LowVirtControllersCount.md b/alerts/openshift-virtualization-operator/LowVirtControllersCount.md
index a246ba2e..2f3e9960 100644
--- a/alerts/openshift-virtualization-operator/LowVirtControllersCount.md
+++ b/alerts/openshift-virtualization-operator/LowVirtControllersCount.md
@@ -25,7 +25,7 @@ OpenShift Virtualization might become completely unresponsive.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Verify that running `virt-controller` pods are available:
@@ -34,17 +34,17 @@ OpenShift Virtualization might become completely unresponsive.
    $ oc -n $NAMESPACE get pods -l kubevirt.io=virt-controller
    ```
 
-3. Check the `virt-launcher` logs for error messages:
+3. Check the `virt-controller` logs for error messages:
 
    ```bash
-   $ oc -n $NAMESPACE logs <virt-launcher>
+   $ oc -n $NAMESPACE logs -l kubevirt.io=virt-controller
    ```
 
-4. Obtain the details of the `virt-launcher` pod to check for status conditions
+4. Obtain the details of the `virt-controller` pod to check for status conditions
 such as unexpected termination or a `NotReady` state.
 
    ```bash
-   $ oc -n $NAMESPACE describe pod/<virt-launcher>
+   $ oc -n $NAMESPACE describe pods -l kubevirt.io=virt-controller
    ```
 
 ## Mitigation
diff --git a/alerts/openshift-virtualization-operator/LowVirtOperatorCount.md b/alerts/openshift-virtualization-operator/LowVirtOperatorCount.md
index 625f3a56..6e1a6435 100644
--- a/alerts/openshift-virtualization-operator/LowVirtOperatorCount.md
+++ b/alerts/openshift-virtualization-operator/LowVirtOperatorCount.md
@@ -29,7 +29,7 @@ VM workloads.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the states of the `virt-operator` pods:
diff --git a/alerts/openshift-virtualization-operator/NetworkAddonsConfigNotReady.md b/alerts/openshift-virtualization-operator/NetworkAddonsConfigNotReady.md
index 580cd9b8..6e783922 100644
--- a/alerts/openshift-virtualization-operator/NetworkAddonsConfigNotReady.md
+++ b/alerts/openshift-virtualization-operator/NetworkAddonsConfigNotReady.md
@@ -18,31 +18,31 @@ Network functionality is affected.
 deployment or daemon set that is not ready:
 
    ```bash
-   $ oc get networkaddonsconfig -o custom-columns="":.status.conditions[*].message
+   $ oc get networkaddonsconfig -o custom-columns=':.status.conditions[*].message' | tr -d '\n'
    ```
 
    Example output:
 
    ```text
-   DaemonSet "cluster-network-addons/macvtap-cni" update is being processed...
+   DaemonSet "openshift-cnv/macvtap-cni" update is being processed...
    ```
 
 2. Check the component's pod for errors:
 
    ```bash
-   $ oc -n cluster-network-addons get daemonset <pod> -o yaml
+   $ oc -n openshift-cnv get daemonset <daemonset> -o yaml
    ```
 
 3. Check the component's logs:
 
    ```bash
-   $ oc -n cluster-network-addons logs <pod>
+   $ oc -n openshift-cnv logs <pod>
    ```
 
 4. Check the component's details for error conditions:
 
    ```bash
-   $ oc -n cluster-network-addons describe <pod>
+   $ oc -n openshift-cnv describe pod <pod>
    ```
 
 ## Mitigation
diff --git a/alerts/openshift-virtualization-operator/NoLeadingVirtOperator.md b/alerts/openshift-virtualization-operator/NoLeadingVirtOperator.md
index 49674d75..ca45a50e 100644
--- a/alerts/openshift-virtualization-operator/NoLeadingVirtOperator.md
+++ b/alerts/openshift-virtualization-operator/NoLeadingVirtOperator.md
@@ -31,7 +31,7 @@ rotation, upgrade, and reconciliation of controllers, might not be available.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Obtain the status of the `virt-operator` pods:
@@ -43,7 +43,7 @@ rotation, upgrade, and reconciliation of controllers, might not be available.
 3. Check the `virt-operator` pod logs to determine the leader status:
 
    ```bash
-   $ oc -n $NAMESPACE logs | grep lead
+   $ oc -n $NAMESPACE logs -l kubevirt.io=virt-operator | grep lead
    ```
 
    Leader pod example:
diff --git a/alerts/openshift-virtualization-operator/NoReadyVirtController.md b/alerts/openshift-virtualization-operator/NoReadyVirtController.md
index 1934f0cf..87f6fcea 100644
--- a/alerts/openshift-virtualization-operator/NoReadyVirtController.md
+++ b/alerts/openshift-virtualization-operator/NoReadyVirtController.md
@@ -21,7 +21,7 @@ launching a new VMI or shutting down an existing VMI.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Verify the number of `virt-controller` devices:
@@ -46,7 +46,7 @@ conditions such as crashing pods or failure to pull images:
 5. Obtain the details of the `virt-controller` pods:
 
    ```bash
-   $ get pods -n $NAMESPACE | grep virt-controller
+   $ oc get pods -n $NAMESPACE | grep virt-controller
    ```
 
 6. Check the logs of the `virt-controller` pods for error messages:
diff --git a/alerts/openshift-virtualization-operator/NoReadyVirtOperator.md b/alerts/openshift-virtualization-operator/NoReadyVirtOperator.md
index 58bb48aa..f5f0a74a 100644
--- a/alerts/openshift-virtualization-operator/NoReadyVirtOperator.md
+++ b/alerts/openshift-virtualization-operator/NoReadyVirtOperator.md
@@ -31,7 +31,7 @@ custom workloads.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Obtain the name of the `virt-operator` deployment:
diff --git a/alerts/openshift-virtualization-operator/OrphanedVirtualMachineInstances.md b/alerts/openshift-virtualization-operator/OrphanedVirtualMachineInstances.md
index 8b6f069d..f774971d 100644
--- a/alerts/openshift-virtualization-operator/OrphanedVirtualMachineInstances.md
+++ b/alerts/openshift-virtualization-operator/OrphanedVirtualMachineInstances.md
@@ -12,24 +12,30 @@ Orphaned VMIs cannot be managed.
 
 ## Diagnosis
 
-1. Check the status of the `virt-handler` pods to view the nodes on which they
+1. Set the `NAMESPACE` environment variable:
+
+   ```bash
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
+   ```
+
+2. Check the status of the `virt-handler` pods to view the nodes on which they
 are running:
 
    ```bash
-   $ oc get pods --all-namespaces -o wide -l kubevirt.io=virt-handler
+   $ oc get pods -n $NAMESPACE -o wide -l kubevirt.io=virt-handler
    ```
 
-2. Check the status of the VMIs to identify VMIs running on nodes that do not
+3. Check the status of the VMIs to identify VMIs running on nodes that do not
 have a running `virt-handler` pod:
 
    ```bash
-   $ oc get vmis --all-namespaces
+   $ oc get vmis -n $NAMESPACE
    ```
 
-3. Check the status of the `virt-handler` daemon:
+4. Check the status of the `virt-handler` daemonset:
 
    ```bash
-   $ oc get daemonset virt-handler --all-namespaces
+   $ oc get daemonsets -n $NAMESPACE -l kubevirt.io=virt-handler
    ```
 
    Example output:
@@ -42,24 +48,24 @@ have a running `virt-handler` pod:
    The daemon set is considered healthy if the `Desired`, `Ready`, and
    `Available` columns contain the same value.
 
-4. If the `virt-handler` daemon set is not healthy, check the `virt-handler`
+5. If the `virt-handler` daemon set is not healthy, check the `virt-handler`
 daemon set for pod deployment issues:
 
    ```bash
-   $ oc get daemonset virt-handler --all-namespaces -o yaml | jq .status
+   $ oc get daemonsets -n $NAMESPACE -o json | jq '.items[] | select(.metadata.name=="virt-handler") | .status'
    ```
 
-5. Check the nodes for issues such as a `NotReady` status:
+6. Check the nodes for issues such as a `NotReady` status:
 
    ```bash
    $ oc get nodes
    ```
 
-6. Check the `spec.workloads` stanza of the `KubeVirt` custom resource (CR) for
+7. Check the `spec.workloads` stanza of the `KubeVirt` custom resource (CR) for
 a workloads placement policy:
 
    ```bash
-   $ oc get kubevirt kubevirt --all-namespaces -o yaml
+   $ oc get kubevirt -n $NAMESPACE -o yaml
    ```
 
 ## Mitigation
diff --git a/alerts/openshift-virtualization-operator/OutdatedVirtualMachineInstanceWorkloads.md b/alerts/openshift-virtualization-operator/OutdatedVirtualMachineInstanceWorkloads.md
index b3d9dc26..49e8f5e3 100644
--- a/alerts/openshift-virtualization-operator/OutdatedVirtualMachineInstanceWorkloads.md
+++ b/alerts/openshift-virtualization-operator/OutdatedVirtualMachineInstanceWorkloads.md
@@ -16,20 +16,26 @@ Outdated VMIs will not receive the security fixes associated with the
 
 ## Diagnosis
 
-1. Identify the outdated VMIs:
+1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ oc get vmi -l kubevirt.io/outdatedLauncherImage --all-namespaces
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
-2. Check the `KubeVirt` custom resource (CR) to determine whether
+2. Identify the outdated VMIs:
+
+   ```bash
+   $ oc get vmi -l kubevirt.io/outdatedLauncherImage -n $NAMESPACE
+   ```
+
+3. Check the `KubeVirt` custom resource (CR) to determine whether
 `workloadUpdateMethods` is configured in the `workloadUpdateStrategy` stanza:
 
    ```bash
-   $ oc get kubevirt --all-namespaces -o yaml
+   $ oc get kubevirt -n $NAMESPACE -o yaml
    ```
 
-3. Check each outdated VMI to determine whether it is live-migratable:
+4. Check each outdated VMI to determine whether it is live-migratable:
 
    ```bash
    $ oc get vmi <vmi> -o yaml
diff --git a/alerts/openshift-virtualization-operator/VirtAPIDown.md b/alerts/openshift-virtualization-operator/VirtAPIDown.md
index ae9dc528..966f3804 100644
--- a/alerts/openshift-virtualization-operator/VirtAPIDown.md
+++ b/alerts/openshift-virtualization-operator/VirtAPIDown.md
@@ -13,7 +13,7 @@ OpenShift Virtualization objects cannot send API calls.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the status of the `virt-api` pods:
diff --git a/alerts/openshift-virtualization-operator/VirtApiRESTErrorsBurst.md b/alerts/openshift-virtualization-operator/VirtApiRESTErrorsBurst.md
index 8d681399..0cbc8eb7 100644
--- a/alerts/openshift-virtualization-operator/VirtApiRESTErrorsBurst.md
+++ b/alerts/openshift-virtualization-operator/VirtApiRESTErrorsBurst.md
@@ -19,7 +19,7 @@ affected.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Obtain the list of `virt-api` pods on your deployment:
@@ -37,7 +37,7 @@ affected.
 4. Obtain the details of the `virt-api` pods:
 
    ```bash
-   $ oc describe -n $NAMESPACE <virt-api>
+   $ oc describe pods -n $NAMESPACE -l kubevirt.io=virt-api
    ```
 
 5. Check if any problems occurred with the nodes. For example, they might be in
diff --git a/alerts/openshift-virtualization-operator/VirtApiRESTErrorsHigh.md b/alerts/openshift-virtualization-operator/VirtApiRESTErrorsHigh.md
index 5c017b9e..6e25beca 100644
--- a/alerts/openshift-virtualization-operator/VirtApiRESTErrorsHigh.md
+++ b/alerts/openshift-virtualization-operator/VirtApiRESTErrorsHigh.md
@@ -18,7 +18,7 @@ affected.
 1. Set the `NAMESPACE` environment variable as follows:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the status of the `virt-api` pods:
@@ -36,7 +36,7 @@ affected.
 4. Obtain the details of the `virt-api` pods:
 
    ```bash
-   $ oc describe -n $NAMESPACE <virt-api>
+   $ oc describe pods -n $NAMESPACE -l kubevirt.io=virt-api
    ```
 
 5. Check if any problems occurred with the nodes. For example, they might be in
diff --git a/alerts/openshift-virtualization-operator/VirtControllerDown.md b/alerts/openshift-virtualization-operator/VirtControllerDown.md
index c66890ba..c551d53c 100644
--- a/alerts/openshift-virtualization-operator/VirtControllerDown.md
+++ b/alerts/openshift-virtualization-operator/VirtControllerDown.md
@@ -13,7 +13,7 @@ an existing VMI.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the status of the `virt-controller` deployment:
diff --git a/alerts/openshift-virtualization-operator/VirtControllerRESTErrorsBurst.md b/alerts/openshift-virtualization-operator/VirtControllerRESTErrorsBurst.md
index f802efef..3dfbb319 100644
--- a/alerts/openshift-virtualization-operator/VirtControllerRESTErrorsBurst.md
+++ b/alerts/openshift-virtualization-operator/VirtControllerRESTErrorsBurst.md
@@ -26,7 +26,7 @@ However, running workloads are not impacted.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. List the available `virt-controller` pods:
diff --git a/alerts/openshift-virtualization-operator/VirtControllerRESTErrorsHigh.md b/alerts/openshift-virtualization-operator/VirtControllerRESTErrorsHigh.md
index 3de52df7..ca7c69bf 100644
--- a/alerts/openshift-virtualization-operator/VirtControllerRESTErrorsHigh.md
+++ b/alerts/openshift-virtualization-operator/VirtControllerRESTErrorsHigh.md
@@ -27,7 +27,7 @@ current status might be delayed.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. List the available `virt-controller` pods:
diff --git a/alerts/openshift-virtualization-operator/VirtHandlerDaemonSetRolloutFailing.md b/alerts/openshift-virtualization-operator/VirtHandlerDaemonSetRolloutFailing.md
index bfbe075a..ef7ce95e 100644
--- a/alerts/openshift-virtualization-operator/VirtHandlerDaemonSetRolloutFailing.md
+++ b/alerts/openshift-virtualization-operator/VirtHandlerDaemonSetRolloutFailing.md
@@ -18,7 +18,7 @@ Identify worker nodes that do not have a running `virt-handler` pod:
 1. Export the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the status of the `virt-handler` pods to identify pods that have not
diff --git a/alerts/openshift-virtualization-operator/VirtHandlerRESTErrorsBurst.md b/alerts/openshift-virtualization-operator/VirtHandlerRESTErrorsBurst.md
index 7abc76ce..9847c10f 100644
--- a/alerts/openshift-virtualization-operator/VirtHandlerRESTErrorsBurst.md
+++ b/alerts/openshift-virtualization-operator/VirtHandlerRESTErrorsBurst.md
@@ -27,7 +27,7 @@ fail. However, running workloads on the affected node are not impacted.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the status of the `virt-handler` pod:
diff --git a/alerts/openshift-virtualization-operator/VirtHandlerRESTErrorsHigh.md b/alerts/openshift-virtualization-operator/VirtHandlerRESTErrorsHigh.md
index 48fd30c9..30218a60 100644
--- a/alerts/openshift-virtualization-operator/VirtHandlerRESTErrorsHigh.md
+++ b/alerts/openshift-virtualization-operator/VirtHandlerRESTErrorsHigh.md
@@ -26,7 +26,7 @@ but reporting their current status might be delayed.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. List the available `virt-handler` pods to identify the failing `virt-handler`
diff --git a/alerts/openshift-virtualization-operator/VirtOperatorDown.md b/alerts/openshift-virtualization-operator/VirtOperatorDown.md
index abc4a5f0..fea7fb30 100644
--- a/alerts/openshift-virtualization-operator/VirtOperatorDown.md
+++ b/alerts/openshift-virtualization-operator/VirtOperatorDown.md
@@ -31,7 +31,7 @@ affect VM workloads.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the status of the `virt-operator` deployment:
diff --git a/alerts/openshift-virtualization-operator/VirtOperatorRESTErrorsBurst.md b/alerts/openshift-virtualization-operator/VirtOperatorRESTErrorsBurst.md
index a09eb764..01d2d6d5 100644
--- a/alerts/openshift-virtualization-operator/VirtOperatorRESTErrorsBurst.md
+++ b/alerts/openshift-virtualization-operator/VirtOperatorRESTErrorsBurst.md
@@ -30,7 +30,7 @@ However, customer workloads, such as virtual machines (VMs) and VM instances
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the status of the `virt-operator` pods:
diff --git a/alerts/openshift-virtualization-operator/VirtOperatorRESTErrorsHigh.md b/alerts/openshift-virtualization-operator/VirtOperatorRESTErrorsHigh.md
index 9e1ab69c..e7b629ce 100644
--- a/alerts/openshift-virtualization-operator/VirtOperatorRESTErrorsHigh.md
+++ b/alerts/openshift-virtualization-operator/VirtOperatorRESTErrorsHigh.md
@@ -28,7 +28,7 @@ However, customer workloads, such as virtual machines (VMs) and VM instances
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
    ```
 
 2. Check the status of the `virt-operator` pods:


Reviews:
user: login: orenc1
body: Hi @c-monaa ,
Thank you very much for your contribution!
Please see my comments below.
There were few recurring comments (mostly for namespace extraction) that I didn't comment on every occurrence of them.
state: CHANGES_REQUESTED
author_association: NONE
submitted_at: 2025-01-21T10:20:51Z
user: login: c-monaa
state: COMMENTED
author_association: NONE
submitted_at: 2025-02-10T11:00:56Z
user: login: c-monaa
state: COMMENTED
author_association: NONE
submitted_at: 2025-02-10T11:01:11Z
user: login: c-monaa
state: COMMENTED
author_association: NONE
submitted_at: 2025-02-10T11:03:03Z
user: login: c-monaa
state: COMMENTED
author_association: NONE
submitted_at: 2025-02-10T11:03:11Z
user: login: orenc1
state: COMMENTED
author_association: NONE
submitted_at: 2025-02-20T08:39:41Z
user: login: orenc1
state: COMMENTED
author_association: NONE
submitted_at: 2025-02-20T08:42:00Z
user: login: orenc1
state: COMMENTED
author_association: NONE
submitted_at: 2025-02-20T08:42:30Z
user: login: c-monaa
state: COMMENTED
author_association: NONE
submitted_at: 2025-02-20T15:10:24Z
user: login: machadovilaca
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-21T14:38:45Z
user: login: c-monaa
state: COMMENTED
author_association: NONE
submitted_at: 2025-03-21T18:25:29Z

Review comments:
diff_hunk: @@ -19,7 +19,7 @@ performance because memory page faults occur during the transition.
 1. Verify that the worker node has sufficient resources:
 
    ```bash
-   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq .items[].status.allocatable
+   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq '.items[].status.allocatable'
path: alerts/openshift-virtualization-operator/KubeVirtVMIExcessiveMigrations.md
user: login: orenc1
body: since the `jq` command has no special characters, no need to surround with quotes.
let's keep it as simple as possible.
created_at: 2025-01-21T09:51:12Z
author_association: NONE
diff_hunk: @@ -42,7 +42,7 @@ performance because memory page faults occur during the transition.
 2. Check the status of the worker node:
 
    ```bash
-   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq .items[].status.conditions
+   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq '.items[].status.conditions'
path: alerts/openshift-virtualization-operator/KubeVirtVMIExcessiveMigrations.md
user: login: orenc1
body: same as above.
created_at: 2025-01-21T09:51:27Z
author_association: NONE
diff_hunk: @@ -21,7 +21,7 @@ launching a new VMI or shutting down an existing VMI.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace | tr -d '\n')"
path: alerts/openshift-virtualization-operator/LowReadyVirtControllersCount.md
user: login: orenc1
body: why not:
```
$ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
```
created_at: 2025-01-21T09:54:21Z
author_association: NONE
diff_hunk: @@ -32,7 +32,7 @@ affect VM workloads.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace | tr -d '\n')"
path: alerts/openshift-virtualization-operator/LowReadyVirtOperatorsCount.md
user: login: orenc1
body: same as above
created_at: 2025-01-21T09:55:27Z
author_association: NONE
diff_hunk: @@ -15,7 +15,7 @@ becomes a single point of failure.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace | tr -d '\n')"
path: alerts/openshift-virtualization-operator/LowVirtAPICount.md
user: login: orenc1
body: same as above
created_at: 2025-01-21T09:55:34Z
author_association: NONE
diff_hunk: @@ -25,7 +25,7 @@ OpenShift Virtualization might become completely unresponsive.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace | tr -d '\n')"
path: alerts/openshift-virtualization-operator/LowVirtControllersCount.md
user: login: orenc1
body: same as above
created_at: 2025-01-21T09:56:11Z
author_association: NONE
diff_hunk: @@ -37,14 +37,14 @@ OpenShift Virtualization might become completely unresponsive.
 3. Check the `virt-launcher` logs for error messages:
 
    ```bash
-   $ oc -n $NAMESPACE logs <virt-launcher>
+   $ oc -n $NAMESPACE logs <virt-controller>
path: alerts/openshift-virtualization-operator/LowVirtControllersCount.md
user: login: orenc1
body: better to use a pod selector:
```
oc -n $NAMESPACE logs -l kubevirt.io=virt-controller
```
also, please fix the description (should be `virt-controller`, not `virt-launcher`)
created_at: 2025-01-21T09:59:09Z
author_association: NONE
diff_hunk: @@ -37,14 +37,14 @@ OpenShift Virtualization might become completely unresponsive.
 3. Check the `virt-launcher` logs for error messages:
 
    ```bash
-   $ oc -n $NAMESPACE logs <virt-launcher>
+   $ oc -n $NAMESPACE logs <virt-controller>
    ```
 
 4. Obtain the details of the `virt-launcher` pod to check for status conditions
 such as unexpected termination or a `NotReady` state.
 
    ```bash
-   $ oc -n $NAMESPACE describe pod/<virt-launcher>
+   $ oc -n $NAMESPACE describe pod/<virt-controller>
path: alerts/openshift-virtualization-operator/LowVirtControllersCount.md
user: login: orenc1
body: ```suggestion
   $ oc -n $NAMESPACE describe pods -l kubevirt.io=virt-controller
```
also, please fix the description (should be `virt-controller`, not `virt-launcher`)
created_at: 2025-01-21T10:00:42Z
author_association: NONE
diff_hunk: @@ -29,7 +29,7 @@ VM workloads.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace | tr -d '\n')"
path: alerts/openshift-virtualization-operator/LowVirtOperatorCount.md
user: login: orenc1
body: ```suggestion
  $ export NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
```
created_at: 2025-01-21T10:01:20Z
author_association: NONE
diff_hunk: @@ -18,7 +18,7 @@ Network functionality is affected.
 deployment or daemon set that is not ready:
 
    ```bash
-   $ oc get networkaddonsconfig -o custom-columns="":.status.conditions[*].message
+   $ oc get networkaddonsconfig -o custom-columns=':.status.conditions[*].message'
path: alerts/openshift-virtualization-operator/NetworkAddonsConfigNotReady.md
user: login: orenc1
body: the new line can be trimmed
```suggestion
  $ oc get networkaddonsconfig -o custom-columns="":.status.conditions[*].message | tr -d '\n'
```
created_at: 2025-01-21T10:06:12Z
author_association: NONE
diff_hunk: @@ -30,7 +30,7 @@ deployment or daemon set that is not ready:
 2. Check the component's pod for errors:
 
    ```bash
-   $ oc -n cluster-network-addons get daemonset <pod> -o yaml
+   $ oc -n cluster-network-addons get daemonset <demonset> -o yaml
path: alerts/openshift-virtualization-operator/NetworkAddonsConfigNotReady.md
user: login: orenc1
body: there is no such namespace `cluster-network-addons`. It should be in the same namespace as kubevirt.
also, typo in `demonset` (should be `daemonset`).
created_at: 2025-01-21T10:09:29Z
author_association: NONE
diff_hunk: @@ -42,7 +42,7 @@ deployment or daemon set that is not ready:
 4. Check the component's details for error conditions:
 
    ```bash
-   $ oc -n cluster-network-addons describe <pod>
+   $ oc -n cluster-network-addons describe pod <pod>
path: alerts/openshift-virtualization-operator/NetworkAddonsConfigNotReady.md
user: login: orenc1
body: no such namespace.
created_at: 2025-01-21T10:10:06Z
author_association: NONE
diff_hunk: @@ -43,7 +43,7 @@ rotation, upgrade, and reconciliation of controllers, might not be available.
 3. Check the `virt-operator` pod logs to determine the leader status:
 
    ```bash
-   $ oc -n $NAMESPACE logs | grep lead
+   $ oc -n $NAMESPACE logs <virt-operator> | grep lead
path: alerts/openshift-virtualization-operator/NoLeadingVirtOperator.md
user: login: orenc1
body: ```suggestion
   $ oc -n $NAMESPACE logs -l kubevirt.io=virt-operator | grep leader
```
created_at: 2025-01-21T10:11:40Z
author_association: NONE
diff_hunk: @@ -29,7 +29,7 @@ have a running `virt-handler` pod:
 3. Check the status of the `virt-handler` daemon:
path: alerts/openshift-virtualization-operator/OrphanedVirtualMachineInstances.md
user: login: orenc1
body: ```suggestion
3. Check the status of the `virt-handler` daemonset:
```
created_at: 2025-01-21T10:12:20Z
author_association: NONE
diff_hunk: @@ -29,7 +29,7 @@ have a running `virt-handler` pod:
 3. Check the status of the `virt-handler` daemon:
 
    ```bash
-   $ oc get daemonset virt-handler --all-namespaces
+   $ oc get daemonsets --all-namespaces | grep virt-handler
path: alerts/openshift-virtualization-operator/OrphanedVirtualMachineInstances.md
user: login: orenc1
body: if you filter the output with grep, you need to update the example output.
but it will be better to use a selector, i.e. `-l kubevirt.io=virt-handler`
created_at: 2025-01-21T10:14:45Z
author_association: NONE
diff_hunk: @@ -59,7 +59,7 @@ daemon set for pod deployment issues:
 a workloads placement policy:
 
    ```bash
-   $ oc get kubevirt kubevirt --all-namespaces -o yaml
+   $ oc get kubevirt -n <namespace> <KubeVirt-name> -o yaml
path: alerts/openshift-virtualization-operator/OrphanedVirtualMachineInstances.md
user: login: orenc1
body: you can omit the kubevirt CR name, as there should be only one in the cluster.
created_at: 2025-01-21T10:17:43Z
author_association: NONE
diff_hunk: @@ -37,7 +37,7 @@ affected.
 4. Obtain the details of the `virt-api` pods:
 
    ```bash
-   $ oc describe -n $NAMESPACE <virt-api>
+   $ oc describe pod -n $NAMESPACE <virt-api>
path: alerts/openshift-virtualization-operator/VirtApiRESTErrorsBurst.md
user: login: orenc1
body: use pod selector here and in step 3
created_at: 2025-01-21T10:18:39Z
author_association: NONE
diff_hunk: @@ -36,7 +36,7 @@ affected.
 4. Obtain the details of the `virt-api` pods:
 
    ```bash
-   $ oc describe -n $NAMESPACE <virt-api>
+   $ oc describe pod -n $NAMESPACE <virt-api>
path: alerts/openshift-virtualization-operator/VirtApiRESTErrorsHigh.md
user: login: orenc1
body: use pod selector here and in step 3
created_at: 2025-01-21T10:19:04Z
author_association: NONE
diff_hunk: @@ -19,7 +19,7 @@ performance because memory page faults occur during the transition.
 1. Verify that the worker node has sufficient resources:
 
    ```bash
-   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq .items[].status.allocatable
+   $ oc get nodes -l node-role.kubernetes.io/worker= -o json | jq '.items[].status.allocatable'
path: alerts/openshift-virtualization-operator/KubeVirtVMIExcessiveMigrations.md
user: login: c-monaa
body: [] are special characters used for filename expansion and without quotes, zsh treats [] as a pattern and tries to match files in the current directory.
Since no matching files are found, it throws an error: "zsh: no matches found: .items[].status.allocatable".
created_at: 2025-02-10T11:00:56Z
author_association: NONE
diff_hunk: @@ -21,7 +21,7 @@ launching a new VMI or shutting down an existing VMI.
 1. Set the `NAMESPACE` environment variable:
 
    ```bash
-   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace)"
+   $ export NAMESPACE="$(oc get kubevirt -A -o custom-columns="":.metadata.namespace | tr -d '\n')"
path: alerts/openshift-virtualization-operator/LowReadyVirtControllersCount.md
user: login: c-monaa
body: That sounds like a better approach to retrieve the namespace.
created_at: 2025-02-10T11:01:11Z
author_association: NONE
diff_hunk: @@ -37,7 +37,7 @@ affected.
 4. Obtain the details of the `virt-api` pods:
 
    ```bash
-   $ oc describe -n $NAMESPACE <virt-api>
+   $ oc describe pod -n $NAMESPACE <virt-api>
path: alerts/openshift-virtualization-operator/VirtApiRESTErrorsBurst.md
user: login: c-monaa
body: Since \<virt-api\> is a pod, we need to specify pod before the pod name, otherwise OpenShift will try to find a resource type named <virt-api>, which doesn’t exist, and return an error: 'the server doesn't have a resource type "virt-api-989bf4c7b-jqsz7"'
created_at: 2025-02-10T11:03:03Z
author_association: NONE
diff_hunk: @@ -36,7 +36,7 @@ affected.
 4. Obtain the details of the `virt-api` pods:
 
    ```bash
-   $ oc describe -n $NAMESPACE <virt-api>
+   $ oc describe pod -n $NAMESPACE <virt-api>
path: alerts/openshift-virtualization-operator/VirtApiRESTErrorsHigh.md
user: login: c-monaa
body: Since \<virt-api\> is a pod, we need to specify pod before the pod name, otherwise OpenShift will try to find a resource type named <virt-api>, which doesn’t exist, and return an error: 'the server doesn't have a resource type "virt-api-989bf4c7b-jqsz7"'
created_at: 2025-02-10T11:03:11Z
author_association: NONE
diff_hunk: @@ -59,7 +59,7 @@ daemon set for pod deployment issues:
 a workloads placement policy:
 
    ```bash
-   $ oc get kubevirt kubevirt --all-namespaces -o yaml
+   $ oc get kubevirt -n <namespace> -o yaml
path: alerts/openshift-virtualization-operator/OrphanedVirtualMachineInstances.md
user: login: orenc1
body: the namespace of the KubeVirt CR can be extracted dynamically, with the command we're using in several places already:
```
NAMESPACE="$(oc get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
```
created_at: 2025-02-20T08:39:40Z
author_association: NONE
diff_hunk: @@ -37,7 +37,7 @@ affected.
 4. Obtain the details of the `virt-api` pods:
 
    ```bash
-   $ oc describe -n $NAMESPACE <virt-api>
+   $ oc describe pod -n $NAMESPACE <virt-api>
path: alerts/openshift-virtualization-operator/VirtApiRESTErrorsBurst.md
user: login: orenc1
body: i meant:
```
$ oc describe pods -n $NAMESPACE -l kubevirt.io=virt-api
```
created_at: 2025-02-20T08:42:00Z
author_association: NONE
diff_hunk: @@ -36,7 +36,7 @@ affected.
 4. Obtain the details of the `virt-api` pods:
 
    ```bash
-   $ oc describe -n $NAMESPACE <virt-api>
+   $ oc describe pod -n $NAMESPACE <virt-api>
path: alerts/openshift-virtualization-operator/VirtApiRESTErrorsHigh.md
user: login: orenc1
body: see previous comment at `alerts/openshift-virtualization-operator/VirtApiRESTErrorsBurst.md`
created_at: 2025-02-20T08:42:29Z
author_association: NONE
diff_hunk: @@ -59,7 +59,7 @@ daemon set for pod deployment issues:
 a workloads placement policy:
 
    ```bash
-   $ oc get kubevirt kubevirt --all-namespaces -o yaml
+   $ oc get kubevirt -n <namespace> -o yaml
path: alerts/openshift-virtualization-operator/OrphanedVirtualMachineInstances.md
user: login: c-monaa
body: I have updated the code to extract the namespace using the suggested command dynamically. Please let me know if you need any more changes.
created_at: 2025-02-20T15:10:23Z
author_association: NONE
diff_hunk: @@ -43,7 +43,7 @@ rotation, upgrade, and reconciliation of controllers, might not be available.
 3. Check the `virt-operator` pod logs to determine the leader status:
 
    ```bash
-   $ oc -n $NAMESPACE logs | grep lead
+   $ oc -n $NAMESPACE logs -l kubevirt.io=virt-operator | grep leader
path: alerts/openshift-virtualization-operator/NoLeadingVirtOperator.md
user: login: machadovilaca
body: we would miss the `Started leading` log
created_at: 2025-03-21T14:38:45Z
author_association: MEMBER
diff_hunk: @@ -43,7 +43,7 @@ rotation, upgrade, and reconciliation of controllers, might not be available.
 3. Check the `virt-operator` pod logs to determine the leader status:
 
    ```bash
-   $ oc -n $NAMESPACE logs | grep lead
+   $ oc -n $NAMESPACE logs -l kubevirt.io=virt-operator | grep leader
path: alerts/openshift-virtualization-operator/NoLeadingVirtOperator.md
user: login: c-monaa
body: I have updated the code so that it works in both ways.
created_at: 2025-03-21T18:25:29Z
author_association: NONE

PR comments:
user: login: openshift-ci[bot]
created_at: 2025-01-20T15:45:25Z
body: Hi @c-monaa. Thanks for your PR.

I'm waiting for a [openshift](https://github.com/orgs/openshift/people) member to verify that this patch is reasonable to test. If it is, they should reply with `/ok-to-test` on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should [join the org](https://github.com/orgs/openshift/people) to skip this step.

Once the patch is verified, the new status will be reflected by the `ok-to-test` label.

I understand the commands that are listed [here](https://go.k8s.io/bot-commands?repo=openshift%2Frunbooks).

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>

author_association: CONTRIBUTOR
user: login: c-monaa
created_at: 2025-01-21T06:28:19Z
body: @apinnick @orenc1 Kindly review the PR
author_association: NONE
user: login: c-monaa
created_at: 2025-02-10T11:18:32Z
body: Hi @orenc1 ,
Thank you so much for your valuable feedback! 
I have made changes based on your suggestions and have also replied to some of your comments where I needed clarification. I’d really appreciate it if you could take a look and share your thoughts.
author_association: NONE
user: login: orenc1
created_at: 2025-03-13T09:05:41Z
body: /ok-to-test
author_association: NONE
user: login: orenc1
created_at: 2025-03-13T09:11:45Z
body: /lgtm
/cc @machadovilaca or @nunnatsa for approving
author_association: NONE
user: login: openshift-ci[bot]
created_at: 2025-03-13T09:11:58Z
body: @orenc1: GitHub didn't allow me to request PR reviews from the following users: for, approving, or.

Note that only [openshift members](https://github.com/orgs/openshift/people) and repo collaborators can review this PR, and authors cannot review their own PRs.

<details>

In response to [this](https://github.com/openshift/runbooks/pull/231#issuecomment-2720519945):

>/lgtm
>/cc @machadovilaca or @nunnatsa for approving


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: CONTRIBUTOR
user: login: machadovilaca
created_at: 2025-03-24T10:03:57Z
body: /approve
author_association: MEMBER
user: login: orenc1
created_at: 2025-03-25T12:50:25Z
body: /lgtm
thanks for your contribution!
author_association: NONE
user: login: openshift-ci[bot]
created_at: 2025-03-25T12:52:34Z
body: [APPROVALNOTIFIER] This PR is **APPROVED**

This pull-request has been approved by: *<a href="https://github.com/openshift/runbooks/pull/231#" title="Author self-approved">c-monaa</a>*, *<a href="https://github.com/openshift/runbooks/pull/231#issuecomment-2747550833" title="Approved">machadovilaca</a>*, *<a href="https://github.com/openshift/runbooks/pull/231#issuecomment-2751155503" title="LGTM">orenc1</a>*

The full list of commands accepted by this bot can be found [here](https://go.k8s.io/bot-commands?repo=openshift%2Frunbooks).

The pull request process is described [here](https://git.k8s.io/community/contributors/guide/owners.md#the-code-review-process)

<details >
Needs approval from an approver in each of these files:

- ~~[alerts/openshift-virtualization-operator/OWNERS](https://github.com/openshift/runbooks/blob/master/alerts/openshift-virtualization-operator/OWNERS)~~ [machadovilaca]

Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
</details>
<!-- META={"approvers":[]} -->
author_association: CONTRIBUTOR
user: login: openshift-ci[bot]
created_at: 2025-03-25T14:08:08Z
body: @c-monaa: all tests **passed!**


[Full PR test history](https://prow.ci.openshift.org/pr-history?org=openshift&repo=runbooks&pr=231). [Your PR dashboard](https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:c-monaa).

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
author_association: CONTRIBUTOR