-
Bug
-
Resolution: Unresolved
-
Undefined
-
MTC 1.8.6
-
None
-
0.42
-
False
-
-
False
-
ToDo
-
-
CNV Storage 267
Description of problem:
Failed to migrate hotplug volume storage class due to spec.accessModes: Unsupported value: "auto"
Version-Release number of selected component (if applicable):
CNV-v4.18.0.rhel9-813, MTC v1.8.6-4
How reproducible:
Always
Steps to Reproduce:
1. Create a fedora vm with ocs-storagecluster-ceph-rbd storage class from InstanceType 2. Create a hotplug dv/pvc with ocs-storagecluster-ceph-rbd storage class --- apiVersion: cdi.kubevirt.io/v1beta1 kind: DataVolume metadata: name: blank-dv spec: source: blank: {} pvc: accessModes: - ReadWriteMany resources: requests: storage: 1Gi storageClassName: ocs-storagecluster-ceph-rbd volumeMode: Block 3. hotplug the volume to vm (without --persist para) $ virtctl addvolume fedora-black-parakeet-14 --volume-name=blank-dv Successfully submitted add volume request to VM fedora-black-parakeet-14 for volume blank-dv 4. Create a migplan and migrate to ocs-storagecluster-ceph-rbd-virtualization storage class, live migration: true, Target volume mode: auto, Target access mode: auto 5. Cutover
Actual results:
Cutover has error: Errors: PersistentVolumeClaim "blank-dv-mig-sc94" is invalid: spec.accessModes: Unsupported value: "auto": supported values: "ReadOnlyMany", "ReadWriteMany", "ReadWriteOnce", "ReadWriteOncePod"
Expected results:
Cutover succeeded.
Additional info:
1. directvolumemigration status:
Status: Conditions: Category: Advisory Durable: true Last Transition Time: 2025-02-10T05:27:27Z Message: The migration has failed. See: Errors. Reason: CreateDestinationPVCs Status: True Type: Failed Errors: PersistentVolumeClaim "blank-dv-mig-sc94" is invalid: spec.accessModes: Unsupported value: "auto": supported values: "ReadOnlyMany", "ReadWriteMany", "ReadWriteOnce", "ReadWriteOncePod" Itinerary: VolumeMigrationFailed Observed Digest: 5e18961c861b297fc1804045cee392b88f5dc0c2597034f011344765ffd20b9f Phase: Completed Phase Description: Complete Start Timestamp: 2025-02-10T05:27:26Z Events: <none>
2. without persist during hotplug the volume to VM, if we set the accessmode RWX and volumemode Block manually (instead of auto) in migplan, the migration keeps pending there
3. if hotplug volume with --persist to the VM, and set Target volume mode: auto, Target access mode: auto, migration succeeded
- links to