diff --git a/docs/deprecated_runbooks/KubeMacPoolDown.md b/docs/deprecated_runbooks/KubeMacPoolDown.md index 0a3fb7a2..15c43da8 100644 --- a/docs/deprecated_runbooks/KubeMacPoolDown.md +++ b/docs/deprecated_runbooks/KubeMacPoolDown.md @@ -43,7 +43,7 @@ If `KubeMacPool` is down, `VirtualMachine` objects cannot be created. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/deprecated_runbooks/KubevirtHyperconvergedClusterOperatorNMOInUseAlert.md b/docs/deprecated_runbooks/KubevirtHyperconvergedClusterOperatorNMOInUseAlert.md index 05de437c..042e8e28 100644 --- a/docs/deprecated_runbooks/KubevirtHyperconvergedClusterOperatorNMOInUseAlert.md +++ b/docs/deprecated_runbooks/KubevirtHyperconvergedClusterOperatorNMOInUseAlert.md @@ -88,7 +88,7 @@ the node. +attaching the artifacts gathered during the diagnosis procedure.--> See the [HCO cluster configuration documentation](https://github.com/kubevirt/hyperconverged-cluster-operator/blob/main/docs/cluster-configuration.md#enablecommonbootimageimport-feature-gate) for more information. diff --git a/docs/runbooks/CDIDataImportCronOutdated.md b/docs/runbooks/CDIDataImportCronOutdated.md index b8409780..e597ea11 100644 --- a/docs/runbooks/CDIDataImportCronOutdated.md +++ b/docs/runbooks/CDIDataImportCronOutdated.md @@ -93,11 +93,10 @@ specification, to poll and import golden images. The updated Containerized Data Importer (CDI) should resolve the issue within a few seconds. 2. If the issue does not resolve itself, or, if you have changed the default -storage class in the cluster, -you must delete the existing boot sources (datavolumes or volumesnapshots) in -the cluster namespace that are configured with the previous default storage -class. The CDI will recreate the data volumes with the newly configured default -storage class. +storage class in the cluster, you must delete the existing boot sources +(datavolumes or volumesnapshots) in the cluster namespace that are configured +with the previous default storage class. The CDI will recreate the data volumes +with the newly configured default storage class. 3. If your cluster is installed in a restricted network environment, disable the `enableCommonBootImageImport` feature gate in order to opt out of automatic @@ -109,7 +108,7 @@ updates: +attaching the artifacts gathered during the diagnosis procedure.--> See the [HCO cluster configuration documentation](https://github.com/kubevirt/hyperconverged-cluster-operator/blob/main/docs/cluster-configuration.md#enablecommonbootimageimport-feature-gate) for more information. diff --git a/docs/runbooks/CDIDataVolumeUnusualRestartCount.md b/docs/runbooks/CDIDataVolumeUnusualRestartCount.md index 6fdc8c8c..f160fa99 100644 --- a/docs/runbooks/CDIDataVolumeUnusualRestartCount.md +++ b/docs/runbooks/CDIDataVolumeUnusualRestartCount.md @@ -13,7 +13,7 @@ issue. ## Diagnosis -1. Find CDI pods with more than three restarts: +1. Find Containerized Data Importer (CDI) pods with more than three restarts: ```bash $ kubectl get pods --all-namespaces -l app=containerized-data-importer -o=jsonpath='{range .items[?(@.status.containerStatuses[0].restartCount>3)]}{.metadata.name}{"/"}{.metadata.namespace}{"\n"}' @@ -37,7 +37,7 @@ Delete the data volume, resolve the issue, and create a new data volume. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/CDIDefaultStorageClassDegraded.md b/docs/runbooks/CDIDefaultStorageClassDegraded.md index 4906c850..ed92c38d 100644 --- a/docs/runbooks/CDIDefaultStorageClassDegraded.md +++ b/docs/runbooks/CDIDefaultStorageClassDegraded.md @@ -2,53 +2,64 @@ ## Meaning -This alert fires when the default (Kubernetes or virtualization) storage class -supports smart clone (either CSI or snapshot based) and ReadWriteMany. +This alert fires when there is no default storage class that supports smart +cloning (CSI or snapshot-based) or the ReadWriteMany access mode. A default virtualization storage class has precedence over a default Kubernetes storage class for creating a VirtualMachine disk image. ## Impact -If the default storage class does not support smart clone, we fallback to -host-assisted cloning, which is the least efficient method of cloning. +If the default storage class does not support smart cloning, the default cloning +method is host-assisted cloning, which is much less efficient. -If the default storage class does not suppprt ReadWriteMany, a virtual machine -using it is not live-migratable. +If the default storage class does not support ReadWriteMany, virtual machines +(VMs) cannot be live migrated. + + ## Diagnosis -Get the default virtualization storage class: +1. Get the default KubeVirt storage class by running the following command: + ```bash $ export CDI_DEFAULT_VIRT_SC="$(kubectl get sc -o json | jq -r '.items[].metadata|select(.annotations."storageclass.kubevirt.io/is-default-virt-class"=="true")|.name')" $ echo default_virt_sc=$CDI_DEFAULT_VIRT_SC ``` -If the default virtualization storage class is set, check if it supports -ReadWriteMany +2. If a default KubeVirt storage class exists, check that it supports +ReadWriteMany by running the following command: + ```bash $ kubectl get storageprofile $CDI_DEFAULT_VIRT_SC -o json | jq '.status.claimPropertySets'| grep ReadWriteMany ``` -Otherwise, if the default virtualization storage class is not set, get the -default Kubernetes storage class: +3. If there is no default KubeVirt storage class, get the default Kubernetes +storage class by running the following command: + ```bash $ export CDI_DEFAULT_K8S_SC="$(kubectl get sc -o json | jq -r '.items[].metadata|select(.annotations."storageclass.kubernetes.io/is-default-class"=="true")|.name')" $ echo default_k8s_sc=$CDI_DEFAULT_K8S_SC ``` -If the default Kubernetes storage class is set, check if it supports -ReadWriteMany: +4. If a default Kubernetes storage class exists, check that it supports +ReadWriteMany by running the following command: + ```bash $ kubectl get storageprofile $CDI_DEFAULT_K8S_SC -o json | jq '.status.claimPropertySets'| grep ReadWriteMany ``` + See [doc](https://github.com/kubevirt/containerized-data-importer/blob/main/doc/efficient-cloning.md) for details about smart clone prerequisites. + ## Mitigation -Ensure that the default storage class supports smart clone and ReadWriteMany. +Ensure that you have a default storage class, either Kubernetes or KubeVirt, and +that the default storage class supports smart cloning and ReadWriteMany. If you cannot resolve the issue, see the following resources: @@ -56,3 +67,7 @@ If you cannot resolve the issue, see the following resources: - [OKD Help](https://www.okd.io/help/) - [#virtualization Slack channel](https://kubernetes.slack.com/channels/virtualization) + + diff --git a/docs/runbooks/CDIMultipleDefaultVirtStorageClasses.md b/docs/runbooks/CDIMultipleDefaultVirtStorageClasses.md index a0ed563e..b9d88c7c 100644 --- a/docs/runbooks/CDIMultipleDefaultVirtStorageClasses.md +++ b/docs/runbooks/CDIMultipleDefaultVirtStorageClasses.md @@ -29,7 +29,7 @@ annotation. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/CDINoDefaultStorageClass.md b/docs/runbooks/CDINoDefaultStorageClass.md index 335da39a..cd69fcf9 100644 --- a/docs/runbooks/CDINoDefaultStorageClass.md +++ b/docs/runbooks/CDINoDefaultStorageClass.md @@ -2,44 +2,50 @@ ## Meaning -This alert fires when there is no default (Kubernetes or virtualization) storage +This alert fires when there is no default (Kubernetes or KubeVirt) storage class, and a data volume is pending for one. -A default virtualization storage class has precedence over a default Kubernetes +A default KubeVirt storage class has precedence over a default Kubernetes storage class for creating a VirtualMachine disk image. ## Impact -If there is no default (k8s or virt) storage class, a data volume that requests -a default storage class (storage class not explicitly specified) will be pending -for one. +If there is no default Kubernetes or KubeVirt storage class, a data volume that +does not have a specified storage class remains in a "pending" state. ## Diagnosis -Get the default Kubernetes storage class: +1. Check for a default Kubernetes storage class by running the following +command: + ```bash $ kubectl get sc -o json | jq '.items[].metadata|select(.annotations."storageclass.kubernetes.io/is-default-class"=="true")|.name' ``` -Get the default virtualization storage class: +2. Check for a default KubeVirt storage class by running the following command: + ```bash $ kubectl get sc -o json | jq '.items[].metadata|select(.annotations."storageclass.kubevirt.io/is-default-virt-class"=="true")|.name' ``` -To set the default Kubernetes storage class if needed: -```bash -$ kubectl patch storageclass -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}' -``` +## Mitigation -To set the default virtualization storage class if needed: -```bash -$ kubectl patch storageclass -p '{"metadata": {"annotations":{"storageclass.kubevirt.io/is-default-virt-class":"true"}}}' -``` +Create a default storage class for either Kubernetes or KubeVirt or for both. -## Mitigation +A default KubeVirt storage class has precedence over a default Kubernetes +storage class for creating a virtual machine disk image. + +* Create a default Kubernetes storage class by running the following command: -Ensure that there is one storage class that has the default (k8s or virt) -storage class annotation. + ```bash + $ kubectl patch storageclass -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}' + ``` + +* Create a default KubeVirt storage class by running the following command: + + ```bash + $ kubectl patch storageclass -p '{"metadata": {"annotations":{"storageclass.kubevirt.io/is-default-virt-class":"true"}}}' + ``` If you cannot resolve the issue, see the following resources: @@ -47,3 +53,7 @@ If you cannot resolve the issue, see the following resources: - [OKD Help](https://www.okd.io/help/) - [#virtualization Slack channel](https://kubernetes.slack.com/channels/virtualization) + + diff --git a/docs/runbooks/CDINotReady.md b/docs/runbooks/CDINotReady.md index cf899378..0d1213ce 100644 --- a/docs/runbooks/CDINotReady.md +++ b/docs/runbooks/CDINotReady.md @@ -2,7 +2,7 @@ ## Meaning -This alert fires when the containerized data importer (CDI) is in a degraded +This alert fires when the Containerized Data Importer (CDI) is in a degraded state: - Not progressing @@ -46,7 +46,7 @@ Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/CDIOperatorDown.md b/docs/runbooks/CDIOperatorDown.md index 63496b5b..c6e14240 100644 --- a/docs/runbooks/CDIOperatorDown.md +++ b/docs/runbooks/CDIOperatorDown.md @@ -42,7 +42,7 @@ installation might not function correctly. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/CDIStorageProfilesIncomplete.md b/docs/runbooks/CDIStorageProfilesIncomplete.md index 918529aa..c6f1b502 100644 --- a/docs/runbooks/CDIStorageProfilesIncomplete.md +++ b/docs/runbooks/CDIStorageProfilesIncomplete.md @@ -37,7 +37,7 @@ for more details about storage profiles. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/CnaoDown.md b/docs/runbooks/CnaoDown.md index 6570f455..922881fd 100644 --- a/docs/runbooks/CnaoDown.md +++ b/docs/runbooks/CnaoDown.md @@ -2,7 +2,7 @@ ## Meaning -This alert fires when the `Cluster-network-addons-operator` (CNAO) is down. +This alert fires when the Cluster Network Addons Operator (CNAO) is down. The CNAO deploys additional networking components on top of the cluster. ## Impact @@ -40,7 +40,7 @@ machine components. As a result, the changes might fail to take effect. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/HCOInstallationIncomplete.md b/docs/runbooks/HCOInstallationIncomplete.md index fcc762ff..c5819fb9 100644 --- a/docs/runbooks/HCOInstallationIncomplete.md +++ b/docs/runbooks/HCOInstallationIncomplete.md @@ -13,19 +13,22 @@ uninstalling the HCO and the HCO is still running. ## Mitigation -Installation: Complete the installation by creating a `HyperConverged` CR with -its default values: - -```bash -$ cat < +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/HPPOperatorDown.md b/docs/runbooks/HPPOperatorDown.md index 502daeb3..d5e6c0e0 100644 --- a/docs/runbooks/HPPOperatorDown.md +++ b/docs/runbooks/HPPOperatorDown.md @@ -40,12 +40,12 @@ result, the HPP installation might not work correctly in the cluster. ## Mitigation -Based on the information obtained during Diagnosis, try to find and resolve the -cause of the issue. +Based on the information obtained during the diagnosis procedure, try to +identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/HPPSharingPoolPathWithOS.md b/docs/runbooks/HPPSharingPoolPathWithOS.md index b5bf5124..62718b88 100644 --- a/docs/runbooks/HPPSharingPoolPathWithOS.md +++ b/docs/runbooks/HPPSharingPoolPathWithOS.md @@ -47,7 +47,7 @@ other circumstances. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/KubeVirtNoAvailableNodesToRunVMs.md b/docs/runbooks/KubeVirtNoAvailableNodesToRunVMs.md index 44e54bc4..6311ee0a 100644 --- a/docs/runbooks/KubeVirtNoAvailableNodesToRunVMs.md +++ b/docs/runbooks/KubeVirtNoAvailableNodesToRunVMs.md @@ -2,7 +2,7 @@ ## Meaning -The KubeVirtNoAvailableNodesToRunVMs alert is triggered when all nodes in the +The `KubeVirtNoAvailableNodesToRunVMs` alert is triggered when all nodes in the Kubernetes cluster are missing hardware virtualization or CPU virtualization extensions. This means that the cluster does not have the necessary hardware support to run virtual machines (VMs). @@ -32,7 +32,7 @@ hardware virtualization or CPU virtualization extensions enabled. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/KubeVirtVMIExcessiveMigrations.md b/docs/runbooks/KubeVirtVMIExcessiveMigrations.md index 42e1f775..1ca58529 100644 --- a/docs/runbooks/KubeVirtVMIExcessiveMigrations.md +++ b/docs/runbooks/KubeVirtVMIExcessiveMigrations.md @@ -103,7 +103,7 @@ If the problem persists, try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/KubemacpoolDown.md b/docs/runbooks/KubemacpoolDown.md index 11b9e9b9..5f4139d3 100644 --- a/docs/runbooks/KubemacpoolDown.md +++ b/docs/runbooks/KubemacpoolDown.md @@ -41,7 +41,7 @@ If `KubeMacPool` is down, `VirtualMachine` objects cannot be created. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/LowReadyVirtControllersCount.md b/docs/runbooks/LowReadyVirtControllersCount.md index fef86cde..079f62d1 100644 --- a/docs/runbooks/LowReadyVirtControllersCount.md +++ b/docs/runbooks/LowReadyVirtControllersCount.md @@ -64,7 +64,7 @@ Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/LowReadyVirtOperatorsCount.md b/docs/runbooks/LowReadyVirtOperatorsCount.md index 4e1ed843..1a40d0fa 100644 --- a/docs/runbooks/LowReadyVirtOperatorsCount.md +++ b/docs/runbooks/LowReadyVirtOperatorsCount.md @@ -55,12 +55,12 @@ affect VM workloads. ## Mitigation -Based on the information obtained during Diagnosis, try to find the cause of the -issue and resolve it. +Based on the information obtained during the diagnosis procedure, try to +identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/LowVirtAPICount.md b/docs/runbooks/LowVirtAPICount.md index 0da42f54..c4afd988 100644 --- a/docs/runbooks/LowVirtAPICount.md +++ b/docs/runbooks/LowVirtAPICount.md @@ -42,7 +42,7 @@ Try to identify the root cause and to resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/LowVirtControllersCount.md b/docs/runbooks/LowVirtControllersCount.md index 64afa12e..db06b996 100644 --- a/docs/runbooks/LowVirtControllersCount.md +++ b/docs/runbooks/LowVirtControllersCount.md @@ -60,7 +60,7 @@ Identify the root cause and fix it, if possible. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/LowVirtOperatorCount.md b/docs/runbooks/LowVirtOperatorCount.md index 6946445a..ec9e957b 100644 --- a/docs/runbooks/LowVirtOperatorCount.md +++ b/docs/runbooks/LowVirtOperatorCount.md @@ -52,12 +52,12 @@ VM workloads. ## Mitigation -Based on the information obtained during Diagnosis, try to find the cause of the -issue and resolve it. +Based on the information obtained during the diagnosis procedure, try to +identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/NetworkAddonsConfigNotReady.md b/docs/runbooks/NetworkAddonsConfigNotReady.md index c1a95a28..506ce153 100644 --- a/docs/runbooks/NetworkAddonsConfigNotReady.md +++ b/docs/runbooks/NetworkAddonsConfigNotReady.md @@ -51,7 +51,7 @@ Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/NoLeadingVirtOperator.md b/docs/runbooks/NoLeadingVirtOperator.md index e553b4f2..a24c0e97 100644 --- a/docs/runbooks/NoLeadingVirtOperator.md +++ b/docs/runbooks/NoLeadingVirtOperator.md @@ -70,12 +70,12 @@ rotation, upgrade, and reconciliation of controllers, might not be available. ## Mitigation -Based on the information obtained during Diagnosis, try to find and resolve the -cause of the issue. +Based on the information obtained during the diagnosis procedure, try to +identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/NoReadyVirtController.md b/docs/runbooks/NoReadyVirtController.md index a9d78a89..c1a6bc20 100644 --- a/docs/runbooks/NoReadyVirtController.md +++ b/docs/runbooks/NoReadyVirtController.md @@ -63,12 +63,12 @@ conditions such as crashing pods or failure to pull images: ## Mitigation -Based on the information obtained during Diagnosis, try to find and resolve the -cause of the issue. +Based on the information obtained during the diagnosis procedure, try to +identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/NoReadyVirtOperator.md b/docs/runbooks/NoReadyVirtOperator.md index 4236ce88..99c17476 100644 --- a/docs/runbooks/NoReadyVirtOperator.md +++ b/docs/runbooks/NoReadyVirtOperator.md @@ -54,12 +54,12 @@ custom workloads. ## Mitigation -Based on the information obtained during Diagnosis, try to find and resolve the -cause of the issue. +Based on the information obtained during the diagnosis procedure, try to +identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/OrphanedVirtualMachineInstances.md b/docs/runbooks/OrphanedVirtualMachineInstances.md index 1ce24505..d6f6bf93 100644 --- a/docs/runbooks/OrphanedVirtualMachineInstances.md +++ b/docs/runbooks/OrphanedVirtualMachineInstances.md @@ -74,7 +74,7 @@ Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> See [How Daemon Pods are scheduled](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#how-daemon-pods-are-scheduled) for more information. diff --git a/docs/runbooks/OutdatedVirtualMachineInstanceWorkloads.md b/docs/runbooks/OutdatedVirtualMachineInstanceWorkloads.md index 3f5251cd..87c3fb75 100644 --- a/docs/runbooks/OutdatedVirtualMachineInstanceWorkloads.md +++ b/docs/runbooks/OutdatedVirtualMachineInstanceWorkloads.md @@ -105,7 +105,7 @@ The VMI is migrated into an updated `virt-launcher` pod. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/SSPDown.md b/docs/runbooks/SSPDown.md index f5039454..eae9f1af 100644 --- a/docs/runbooks/SSPDown.md +++ b/docs/runbooks/SSPDown.md @@ -45,7 +45,7 @@ might not be updated or reset if they fail. Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/SSPFailingToReconcile.md b/docs/runbooks/SSPFailingToReconcile.md index 84e1c6c7..7248e018 100644 --- a/docs/runbooks/SSPFailingToReconcile.md +++ b/docs/runbooks/SSPFailingToReconcile.md @@ -57,7 +57,7 @@ might not be updated or reset if they fail. Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/SSPHighRateRejectedVms.md b/docs/runbooks/SSPHighRateRejectedVms.md index 4c7a29a9..f02f4334 100644 --- a/docs/runbooks/SSPHighRateRejectedVms.md +++ b/docs/runbooks/SSPHighRateRejectedVms.md @@ -39,7 +39,7 @@ cause: Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/SSPOperatorDown.md b/docs/runbooks/SSPOperatorDown.md index 16b93aca..1ff336a6 100644 --- a/docs/runbooks/SSPOperatorDown.md +++ b/docs/runbooks/SSPOperatorDown.md @@ -45,7 +45,7 @@ might not be updated or reset if they fail. Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/SSPTemplateValidatorDown.md b/docs/runbooks/SSPTemplateValidatorDown.md index 52198dcd..09ca0383 100644 --- a/docs/runbooks/SSPTemplateValidatorDown.md +++ b/docs/runbooks/SSPTemplateValidatorDown.md @@ -43,7 +43,7 @@ with specifications that do not match their respective workloads. Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtAPIDown.md b/docs/runbooks/VirtAPIDown.md index a5893502..a1b3e725 100644 --- a/docs/runbooks/VirtAPIDown.md +++ b/docs/runbooks/VirtAPIDown.md @@ -46,7 +46,7 @@ image pull failures: Try to identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtApiRESTErrorsBurst.md b/docs/runbooks/VirtApiRESTErrorsBurst.md index 568741e5..9019bdce 100644 --- a/docs/runbooks/VirtApiRESTErrorsBurst.md +++ b/docs/runbooks/VirtApiRESTErrorsBurst.md @@ -61,12 +61,12 @@ a `NotReady` state: ## Mitigation -Based on the information obtained during Diagnosis, try to identify the root -cause and resolve the issue. +Based on the information obtained during the diagnosis procedure, try to +identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtApiRESTErrorsHigh.md b/docs/runbooks/VirtApiRESTErrorsHigh.md index 7c56f387..8230ac10 100644 --- a/docs/runbooks/VirtApiRESTErrorsHigh.md +++ b/docs/runbooks/VirtApiRESTErrorsHigh.md @@ -60,12 +60,12 @@ a `NotReady` state: ## Mitigation -Based on the information obtained during Diagnosis, try to identify the root -cause and resolve the issue. +Based on the information obtained during the diagnosis procedure, try to +identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtControllerDown.md b/docs/runbooks/VirtControllerDown.md index a1727724..bdd14954 100644 --- a/docs/runbooks/VirtControllerDown.md +++ b/docs/runbooks/VirtControllerDown.md @@ -43,7 +43,7 @@ Identify the root cause and fix it, if possible. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtControllerRESTErrorsBurst.md b/docs/runbooks/VirtControllerRESTErrorsBurst.md index 32f2d65e..a70216bb 100644 --- a/docs/runbooks/VirtControllerRESTErrorsBurst.md +++ b/docs/runbooks/VirtControllerRESTErrorsBurst.md @@ -53,7 +53,7 @@ $ kubectl delete -n $NAMESPACE +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtControllerRESTErrorsHigh.md b/docs/runbooks/VirtControllerRESTErrorsHigh.md index 30741970..1928e3a7 100644 --- a/docs/runbooks/VirtControllerRESTErrorsHigh.md +++ b/docs/runbooks/VirtControllerRESTErrorsHigh.md @@ -54,7 +54,7 @@ $ kubectl delete -n $NAMESPACE +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtHandlerRESTErrorsBurst.md b/docs/runbooks/VirtHandlerRESTErrorsBurst.md index dfc2c6bc..093203d0 100644 --- a/docs/runbooks/VirtHandlerRESTErrorsBurst.md +++ b/docs/runbooks/VirtHandlerRESTErrorsBurst.md @@ -54,7 +54,7 @@ $ kubectl delete -n $NAMESPACE +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtHandlerRESTErrorsHigh.md b/docs/runbooks/VirtHandlerRESTErrorsHigh.md index 9d6def47..cf4fa222 100644 --- a/docs/runbooks/VirtHandlerRESTErrorsHigh.md +++ b/docs/runbooks/VirtHandlerRESTErrorsHigh.md @@ -60,7 +60,7 @@ $ kubectl delete -n $NAMESPACE +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtOperatorDown.md b/docs/runbooks/VirtOperatorDown.md index 387eb328..539ce6cd 100644 --- a/docs/runbooks/VirtOperatorDown.md +++ b/docs/runbooks/VirtOperatorDown.md @@ -60,12 +60,12 @@ affect VM workloads. ## Mitigation -Based on the information obtained during Diagnosis, try to find and resolve the -cause of the issue. +Based on the information obtained during the diagnosis procedure, try to +identify the root cause and resolve the issue. +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtOperatorRESTErrorsBurst.md b/docs/runbooks/VirtOperatorRESTErrorsBurst.md index 6311cb55..42a71c9c 100644 --- a/docs/runbooks/VirtOperatorRESTErrorsBurst.md +++ b/docs/runbooks/VirtOperatorRESTErrorsBurst.md @@ -62,7 +62,7 @@ $ kubectl delete -n $NAMESPACE +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: diff --git a/docs/runbooks/VirtOperatorRESTErrorsHigh.md b/docs/runbooks/VirtOperatorRESTErrorsHigh.md index 0e67d974..9de2e8c3 100644 --- a/docs/runbooks/VirtOperatorRESTErrorsHigh.md +++ b/docs/runbooks/VirtOperatorRESTErrorsHigh.md @@ -60,7 +60,7 @@ $ kubectl delete -n +attaching the artifacts gathered during the diagnosis procedure.--> If you cannot resolve the issue, see the following resources: