OpenShift Virtualization workaround (#200)

Signed-off-by: Michael Mattsson <[email protected]>

docs/csi_driver/index.md

@@ -299,6 +299,7 @@ HPE currently supports up to three minor releases of the HPE CSI Driver for Kube
 * The CSI driver support a fixed number of volumes per node. Inspect the current limitation by running `kubectl get csinodes -o yaml` and inspect `.spec.drivers.allocatable` for "csi.hpe.com". The "count" element contains how many volumes the node can attach from the HPE CSI Driver (default is 100).
 * The HPE CSI Driver uses host networking for the node driver. Some CNIs have flaky implementations which prevents the CSI driver components to communicate properly. Especially notorious is Flannel on K3s. Use Calico if possible for the widest compatibility.
 * The [NFS Server Provisioner](using.md#limitations_and_considerations_for_the_nfs_server_provisioner) and each of the [CSPs](../container_storage_provider/index.md) have known limitations listed separately.
+* The HPE CSI Driver does not support access mode transformations. I.e, it's not possible to clone an "RWO" volume into an "RWX" volume or vice versa. See [this note](../partners/redhat_openshift/index.md#storageprofile_for_openshift_virtualization_source_pvcs) on how to work around this limitation with OpenShift Virtualization.
 
 ## iSCSI CHAP Considerations
 

docs/partners/redhat_openshift/index.md

@@ -33,7 +33,7 @@ Check the table above periodically for future releases.
     - Other combinations may work but will not be supported.
     - Both Red Hat Enterprise Linux and Red Hat CoreOS worker nodes are supported.
     - Instructions on this page only reflect the current stable version of the HPE CSI Operator and OpenShift.
-    - OpenShift Virtualization OS images are only supported on `PVCs` using "RWX" with `volumeMode: Block`.
+    - OpenShift Virtualization OS images are only supported on `PVCs` using "RWX" with `volumeMode: Block`. See [below](#storageprofile_for_openshift_virtualization_source_pvcs) for more details.
 
 ### Security model
 
@@ -265,9 +265,44 @@ parameters:
 ...
 ```
 
+## StorageProfile for OpenShift Virtualization Source PVCs
+
+If OpenShift Virtualization is being used and Live Migration is desired for virtual machines `PVCs` cloned from the "openshift-virtualization-os-images" `Namespace`, the `StorageProfile` needs to be updated to "ReadWriteMany".
+
+If the default `StorageClass` is named "hpe-standard", issue the following command:
+
+```text
+oc edit -n openshift-cnv storageprofile hpe-standard
+```
+
+Replace the `spec: {}` with the following:
+
+```yaml
+spec:
+  claimPropertySets:
+  - accessModes:
+    - ReadWriteMany
+    volumeMode: Block
+```
+
+Ensure there are no errors. Recreate the OS images:
+
+```text
+oc delete pvc -n openshift-virtualization-os-images --all
+```
+
+Inspect the `PVCs` and ensure they are re-created with "RWX":
+
+```text
+oc get pvc -n openshift-virtualization-os-images -w
+```
+
+!!! hint
+    These steps might be removed in a future release in the event access mode transformation become a supported feature of the CSI driver.
+
 # Unsupported Helm Chart Install
 
-In the event Red Hat releases a new release of OpenShift between HPE CSI Driver releases or if interest arises to run the HPE CSI Driver on an uncertified version of OpenShift, it's possible to install the CSI driver using the Helm chart instead.
+In the event Red Hat releases a new version of OpenShift between HPE CSI Driver releases or if interest arises to run the HPE CSI Driver on an uncertified version of OpenShift, it's possible to install the CSI driver using the Helm chart instead.
 
 It's not recommended to install the Helm chart unless it's listed as "Field Tested" in the [support matrix](#certified_combinations) above.