-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
Incidents & Support
-
0.42
-
False
-
-
False
-
-
Storage Core Sprint 244, Storage Core Sprint 246
-
Moderate
-
No
Description of problem:
When attempting to Clone a Data volume across storage classes, the clone hangs indefinitely.
We see the source pod failing with:
4h24m Warning FailedMapVolume pod/3bc29af2-75a5-4b20-bd1e-42ce1e280c16-source-pod MapVolume.MapPodDevice failed for volume "csivol-ec0afd0f5c" : rpc error: code = InvalidArgument desc = read only not supported for Block Volume
Version-Release number of selected component (if applicable):
4.12
How reproducible:
Steps to Reproduce:
Dell storage profile: kind: StorageProfile spec: claimPropertySets: - accessModes: - ReadWriteOnce volumeMode: Block - accessModes: - ReadWriteOnce volumeMode: Filesystem cloneStrategy: csi-clone status: claimPropertySets: - accessModes: - ReadWriteOnce volumeMode: Block - accessModes: - ReadWriteOnce volumeMode: Filesystem cloneStrategy: csi-clone provisioner: csi-powerstore.dellemc.com storageClass: powerstore-xfs-iscsi-sc Create source pvc in above storage class oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE openstack-base-img Bound csivol-ec0afd0f5c 500Gi RWO powerstore-xfs-iscsi-sc 17d Try to deploy new VM to a different storage class using the above pvc as the source: spec: pvc: accessModes: - ReadWriteMany resources: requests: storage: 500Gi storageClassName: powerstore-nfs1-ocp-sc volumeMode: Filesystem source: pvc: name: openstack-base-img namespace: openstack There is a previous Bug which describes this exact scenario: https://bugzilla.redhat.com/show_bug.cgi?id=2087784 Bug was previously closed. The current customer would like this to work. We understand this boils down to the Dell storage driver rejecting an attempt to mount the source ReadOnly and either the driver needs to allow this, or Shift needs to handle this scenario better. We have worked around this by putting the source on the same storage as the destination, but this is not what the customer wants moving forward.
Actual results:
Expected results:
Deploy of VM and clone works successfully
Additional info:
This is tied to a customer case which I'll share in another update for access to logs if needed.
- links to
-
RHEA-2023:116760 OpenShift Virtualization 4.15.0 Images
- mentioned on