-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Incidents & Support
-
False
-
-
False
-
-
-
Important
Description of problem:
As per doc , to avoid copying the shared disk during migration, we have to pass the "migrateSharedDisks: false" while migrating the second VM, and MTV should automatically find the shared disk from existing PVCs and should attach it to the VM.
However, this is not working while using storage offloading. It's because the PVCs are not created with "Shareable: true" flag which is required for MTV to find the shareable disk as per https://github.com/kubev2v/forklift/blob/v2.10.4/pkg/controller/plan/adapter/vsphere/utils.go#L95
Version-Release number of selected component (if applicable):
mtv-operator.v2.10.5
How reproducible:
Observed in customer's env. I can also see the same in the lab where PVCs are not created with the label "Shareable: true" while using offloading. I don't have a storage offloading capable lab to do the end to end migration.
Steps to Reproduce:
1. Enable storage offloading on the cluster. 2. Migrate the first VM with the shareable disk with option "migrateSharedDisks: true" 3. Check the "shareable" PVC for the Shareable label. It will not be available. 4. Migrate the second VM with "migrateSharedDisks: false". The "shareable" disk will not be attached to the VM and the logs have error "Failed to find shared PVCs"
Actual results:
Shareable disk is not automatically attached to the second VM while using storage offloading
Expected results:
Additional info:
