Merge pull request #56128 from apinnick/4.13-CNV-runbooks

Update CNV runbook module anchor IDs for 4.13

Author: apinnick

modules/virt-runbook-cdidataimportcronoutdated.adoc

@@ -1,14 +1,15 @@
-// Automatically generated by 'runbook-conversion.sh'. Do not edit.
+// Do not edit this module. It is generated with a script.
+// Do not reuse this module. The anchor IDs do not contain a context statement.
 // Module included in the following assemblies:
 //
 // * virt/logging_events_monitoring/virt-runbooks.adoc
 
 :_content-type: REFERENCE
-[id="virt-runbook-cdidataimportcronoutdated_{context}"]
+[id="virt-runbook-CDIDataImportCronOutdated"]
 = CDIDataImportCronOutdated
 
 [discrete]
-[id="meaning-cdidataimportcronoutdated_{context}"]
+[id="meaning-cdidataimportcronoutdated"]
 == Meaning
 
 This alert fires when `DataImportCron` cannot poll or import the latest disk
@@ -24,15 +25,15 @@ distribution. For other disk images, _latest_ refers to the latest hash of the
 image that is available.
 
 [discrete]
-[id="impact-cdidataimportcronoutdated_{context}"]
+[id="impact-cdidataimportcronoutdated"]
 == Impact
 
 VMs might be created from outdated disk images.
 
 VMs might fail to start because no source PVC is available for cloning.
 
 [discrete]
-[id="diagnosis-cdidataimportcronoutdated_{context}"]
+[id="diagnosis-cdidataimportcronoutdated"]
 == Diagnosis
 
 . Check the cluster for a default storage class:
@@ -112,7 +113,7 @@ $ oc logs -n $CDI_NAMESPACE deployment/cdi-deployment
 ----
 
 [discrete]
-[id="mitigation-cdidataimportcronoutdated_{context}"]
+[id="mitigation-cdidataimportcronoutdated"]
 == Mitigation
 
 . Set a default storage class, either on the cluster or in the `DataImportCron`

modules/virt-runbook-cdidatavolumeunusualrestartcount.adoc

@@ -1,21 +1,22 @@
-// Automatically generated by 'runbook-conversion.sh'. Do not edit.
+// Do not edit this module. It is generated with a script.
+// Do not reuse this module. The anchor IDs do not contain a context statement.
 // Module included in the following assemblies:
 //
 // * virt/logging_events_monitoring/virt-runbooks.adoc
 
 :_content-type: REFERENCE
-[id="virt-runbook-cdidatavolumeunusualrestartcount_{context}"]
+[id="virt-runbook-CDIDataVolumeUnusualRestartCount"]
 = CDIDataVolumeUnusualRestartCount
 
 [discrete]
-[id="meaning-cdidatavolumeunusualrestartcount_{context}"]
+[id="meaning-cdidatavolumeunusualrestartcount"]
 == Meaning
 
 This alert fires when a `DataVolume` object restarts more than three
 times.
 
 [discrete]
-[id="impact-cdidatavolumeunusualrestartcount_{context}"]
+[id="impact-cdidatavolumeunusualrestartcount"]
 == Impact
 
 Data volumes are responsible for importing and creating a virtual
@@ -24,7 +25,7 @@ more than three times, these operations are unlikely to succeed. You
 must diagnose and resolve the issue.
 
 [discrete]
-[id="diagnosis-cdidatavolumeunusualrestartcount_{context}"]
+[id="diagnosis-cdidatavolumeunusualrestartcount"]
 == Diagnosis
 
 . Obtain the name and namespace of the data volume:
@@ -59,7 +60,7 @@ $ oc -n <namespace> describe logs <pod>
 ----
 
 [discrete]
-[id="mitigation-cdidatavolumeunusualrestartcount_{context}"]
+[id="mitigation-cdidatavolumeunusualrestartcount"]
 == Mitigation
 
 Delete the data volume, resolve the issue, and create a new data volume.

modules/virt-runbook-cdinotready.adoc

@@ -1,14 +1,15 @@
-// Automatically generated by 'runbook-conversion.sh'. Do not edit.
+// Do not edit this module. It is generated with a script.
+// Do not reuse this module. The anchor IDs do not contain a context statement.
 // Module included in the following assemblies:
 //
 // * virt/logging_events_monitoring/virt-runbooks.adoc
 
 :_content-type: REFERENCE
-[id="virt-runbook-cdinotready_{context}"]
+[id="virt-runbook-CDINotReady"]
 = CDINotReady
 
 [discrete]
-[id="meaning-cdinotready_{context}"]
+[id="meaning-cdinotready"]
 == Meaning
 
 This alert fires when the Containerized Data Importer (CDI) is in
@@ -18,7 +19,7 @@ a degraded state:
 * Not available to use
 
 [discrete]
-[id="impact-cdinotready_{context}"]
+[id="impact-cdinotready"]
 == Impact
 
 CDI is not usable, so users cannot build virtual machine disks on
@@ -27,7 +28,7 @@ CDI components are not ready and they stopped progressing towards
 a ready state.
 
 [discrete]
-[id="diagnosis-cdinotready_{context}"]
+[id="diagnosis-cdinotready"]
 == Diagnosis
 
 . Set the `CDI_NAMESPACE` environment variable:
@@ -60,7 +61,7 @@ $ oc -n $CDI_NAMESPACE logs <pod>
 ----
 
 [discrete]
-[id="mitigation-cdinotready_{context}"]
+[id="mitigation-cdinotready"]
 == Mitigation
 
 Try to identify the root cause and resolve the issue.

modules/virt-runbook-cdioperatordown.adoc

@@ -1,14 +1,15 @@
-// Automatically generated by 'runbook-conversion.sh'. Do not edit.
+// Do not edit this module. It is generated with a script.
+// Do not reuse this module. The anchor IDs do not contain a context statement.
 // Module included in the following assemblies:
 //
 // * virt/logging_events_monitoring/virt-runbooks.adoc
 
 :_content-type: REFERENCE
-[id="virt-runbook-cdioperatordown_{context}"]
+[id="virt-runbook-CDIOperatorDown"]
 = CDIOperatorDown
 
 [discrete]
-[id="meaning-cdioperatordown_{context}"]
+[id="meaning-cdioperatordown"]
 == Meaning
 
 This alert fires when the Containerized Data Importer (CDI) Operator is down.
@@ -17,14 +18,14 @@ as data volume and persistent volume claim (PVC) controllers. These controllers
 help users build virtual machine disks on PVCs.
 
 [discrete]
-[id="impact-cdioperatordown_{context}"]
+[id="impact-cdioperatordown"]
 == Impact
 
 The CDI components might fail to deploy or to stay in a required state. The
 CDI installation might not function correctly.
 
 [discrete]
-[id="diagnosis-cdioperatordown_{context}"]
+[id="diagnosis-cdioperatordown"]
 == Diagnosis
 
 . Set the `CDI_NAMESPACE` environment variable:
@@ -57,7 +58,7 @@ $ oc -n $CDI_NAMESPACE logs -l name=cdi-operator
 ----
 
 [discrete]
-[id="mitigation-cdioperatordown_{context}"]
+[id="mitigation-cdioperatordown"]
 == Mitigation
 
 If you cannot resolve the issue, log in to the

modules/virt-runbook-cdistorageprofilesincomplete.adoc

@@ -1,14 +1,15 @@
-// Automatically generated by 'runbook-conversion.sh'. Do not edit.
+// Do not edit this module. It is generated with a script.
+// Do not reuse this module. The anchor IDs do not contain a context statement.
 // Module included in the following assemblies:
 //
 // * virt/logging_events_monitoring/virt-runbooks.adoc
 
 :_content-type: REFERENCE
-[id="virt-runbook-cdistorageprofilesincomplete_{context}"]
+[id="virt-runbook-CDIStorageProfilesIncomplete"]
 = CDIStorageProfilesIncomplete
 
 [discrete]
-[id="meaning-cdistorageprofilesincomplete_{context}"]
+[id="meaning-cdistorageprofilesincomplete"]
 == Meaning
 
 This alert fires when a Containerized Data Importer (CDI) storage profile is
@@ -19,13 +20,13 @@ If a storage profile is incomplete, the CDI cannot infer persistent volume claim
 create a virtual machine (VM) disk.
 
 [discrete]
-[id="impact-cdistorageprofilesincomplete_{context}"]
+[id="impact-cdistorageprofilesincomplete"]
 == Impact
 
 The CDI cannot create a VM disk on the PVC.
 
 [discrete]
-[id="diagnosis-cdistorageprofilesincomplete_{context}"]
+[id="diagnosis-cdistorageprofilesincomplete"]
 == Diagnosis
 
 * Identify the incomplete storage profile:
@@ -36,7 +37,7 @@ $ oc get storageprofile <storage_class>
 ----
 
 [discrete]
-[id="mitigation-cdistorageprofilesincomplete_{context}"]
+[id="mitigation-cdistorageprofilesincomplete"]
 == Mitigation
 
 * Add the missing storage profile information as in the following

modules/virt-runbook-cnaodown.adoc

@@ -1,28 +1,29 @@
-// Automatically generated by 'runbook-conversion.sh'. Do not edit.
+// Do not edit this module. It is generated with a script.
+// Do not reuse this module. The anchor IDs do not contain a context statement.
 // Module included in the following assemblies:
 //
 // * virt/logging_events_monitoring/virt-runbooks.adoc
 
 :_content-type: REFERENCE
-[id="virt-runbook-cnaodown_{context}"]
+[id="virt-runbook-CnaoDown"]
 = CnaoDown
 
 [discrete]
-[id="meaning-cnaodown_{context}"]
+[id="meaning-cnaodown"]
 == Meaning
 
 This alert fires when the Cluster Network Addons Operator (CNAO) is down.
 The CNAO deploys additional networking components on top of the cluster.
 
 [discrete]
-[id="impact-cnaodown_{context}"]
+[id="impact-cnaodown"]
 == Impact
 
 If the CNAO is not running, the cluster cannot reconcile changes to virtual
 machine components. As a result, the changes might fail to take effect.
 
 [discrete]
-[id="diagnosis-cnaodown_{context}"]
+[id="diagnosis-cnaodown"]
 == Diagnosis
 
 . Set the `NAMESPACE` environment variable:
@@ -55,7 +56,7 @@ $ oc -n $NAMESPACE describe pods -l name=cluster-network-addons-operator
 ----
 
 [discrete]
-[id="mitigation-cnaodown_{context}"]
+[id="mitigation-cnaodown"]
 == Mitigation
 
 If you cannot resolve the issue, log in to the

modules/virt-runbook-hppnotready.adoc

@@ -1,14 +1,15 @@
-// Automatically generated by 'runbook-conversion.sh'. Do not edit.
+// Do not edit this module. It is generated with a script.
+// Do not reuse this module. The anchor IDs do not contain a context statement.
 // Module included in the following assemblies:
 //
 // * virt/logging_events_monitoring/virt-runbooks.adoc
 
 :_content-type: REFERENCE
-[id="virt-runbook-hppnotready_{context}"]
+[id="virt-runbook-HPPNotReady"]
 = HPPNotReady
 
 [discrete]
-[id="meaning-hppnotready_{context}"]
+[id="meaning-hppnotready"]
 == Meaning
 
 This alert fires when a hostpath provisioner (HPP) installation is in a
@@ -18,14 +19,14 @@ The HPP dynamically provisions hostpath volumes to provide storage for
 persistent volume claims (PVCs).
 
 [discrete]
-[id="impact-hppnotready_{context}"]
+[id="impact-hppnotready"]
 == Impact
 
 HPP is not usable. Its components are not ready and they are not progressing
 towards a ready state.
 
 [discrete]
-[id="diagnosis-hppnotready_{context}"]
+[id="diagnosis-hppnotready"]
 == Diagnosis
 
 . Set the `HPP_NAMESPACE` environment variable:
@@ -58,7 +59,7 @@ $ oc -n $HPP_NAMESPACE logs <pod>
 ----
 
 [discrete]
-[id="mitigation-hppnotready_{context}"]
+[id="mitigation-hppnotready"]
 == Mitigation
 
 Based on the information obtained during the diagnosis procedure, try to

modules/virt-runbook-hppoperatordown.adoc

@@ -1,14 +1,15 @@
-// Automatically generated by 'runbook-conversion.sh'. Do not edit.
+// Do not edit this module. It is generated with a script.
+// Do not reuse this module. The anchor IDs do not contain a context statement.
 // Module included in the following assemblies:
 //
 // * virt/logging_events_monitoring/virt-runbooks.adoc
 
 :_content-type: REFERENCE
-[id="virt-runbook-hppoperatordown_{context}"]
+[id="virt-runbook-HPPOperatorDown"]
 = HPPOperatorDown
 
 [discrete]
-[id="meaning-hppoperatordown_{context}"]
+[id="meaning-hppoperatordown"]
 == Meaning
 
 This alert fires when the hostpath provisioner (HPP) Operator is down.
@@ -17,14 +18,14 @@ The HPP Operator deploys and manages the HPP infrastructure components, such
 as the daemon set that provisions hostpath volumes.
 
 [discrete]
-[id="impact-hppoperatordown_{context}"]
+[id="impact-hppoperatordown"]
 == Impact
 
 The HPP components might fail to deploy or to remain in the required state.
 As a result, the HPP installation might not work correctly in the cluster.
 
 [discrete]
-[id="diagnosis-hppoperatordown_{context}"]
+[id="diagnosis-hppoperatordown"]
 == Diagnosis
 
 . Configure the `HPP_NAMESPACE` environment variable:
@@ -57,7 +58,7 @@ $ oc -n $HPP_NAMESPACE logs -l name=hostpath-provisioner-operator
 ----
 
 [discrete]
-[id="mitigation-hppoperatordown_{context}"]
+[id="mitigation-hppoperatordown"]
 == Mitigation
 
 Based on the information obtained during the diagnosis procedure, try to