|
| 1 | +// Do not edit this module. It is generated with a script. |
| 2 | +// Do not reuse this module. The anchor IDs do not contain a context statement. |
| 3 | +// Module included in the following assemblies: |
| 4 | +// |
| 5 | +// * virt/monitoring/virt-runbooks.adoc |
| 6 | + |
| 7 | +:_mod-docs-content-type: REFERENCE |
| 8 | +[id="virt-runbook-CDIMultipleDefaultVirtStorageClasses"] |
| 9 | += CDIMultipleDefaultVirtStorageClasses |
| 10 | + |
| 11 | +[discrete] |
| 12 | +[id="meaning-cdimultipledefaultvirtstorageclasses"] |
| 13 | +== Meaning |
| 14 | + |
| 15 | +This alert fires when more than one storage class has the annotation |
| 16 | +`storageclass.kubevirt.io/is-default-virt-class: "true"`. |
| 17 | + |
| 18 | +[discrete] |
| 19 | +[id="impact-cdimultipledefaultvirtstorageclasses"] |
| 20 | +== Impact |
| 21 | + |
| 22 | +The `storageclass.kubevirt.io/is-default-virt-class: "true"` annotation |
| 23 | +defines a default {VirtProductName} storage class. |
| 24 | + |
| 25 | +If more than one default {VirtProductName} storage class |
| 26 | +is defined, a data volume with no storage class specified |
| 27 | +receives the most recently created default storage class. |
| 28 | + |
| 29 | +[discrete] |
| 30 | +[id="diagnosis-cdimultipledefaultvirtstorageclasses"] |
| 31 | +== Diagnosis |
| 32 | + |
| 33 | +Obtain a list of default {VirtProductName} storage classes by running |
| 34 | +the following command: |
| 35 | + |
| 36 | +[source,terminal] |
| 37 | +---- |
| 38 | +$ oc get sc -o jsonpath='{.items[?(@.metadata.annotations.storageclass\.kubevirt\.io/is-default-virt-class=="true")].metadata.name}' |
| 39 | +---- |
| 40 | + |
| 41 | +[discrete] |
| 42 | +[id="mitigation-cdimultipledefaultvirtstorageclasses"] |
| 43 | +== Mitigation |
| 44 | + |
| 45 | +Ensure that only one default {VirtProductName} storage class |
| 46 | +is defined by removing the annotation from the other storage classes. |
| 47 | + |
| 48 | +If you cannot resolve the issue, log in to the |
| 49 | +link:https://access.redhat.com[Customer Portal] and open a support case, attaching |
| 50 | +the artifacts gathered during the diagnosis procedure. |
0 commit comments