-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
2
-
False
-
-
False
-
None
-
-
CNV Storage Sprint 285
-
Low
-
Customer Reported
-
None
Description of problem:
As discussed in MIG-1869 and CNV-80398, in 4.21 the migration controller in CNV is not checking the PVCs for the existing of the annotation below. But in 4.20 and lower MTC did check that and according to the discussions checking for the annotation is the correct behaviour.
cdi.kubevirt.io/storage.contentType: kubevirt
Version-Release number of selected component (if applicable):
4.21
How reproducible:
Always
Steps to Reproduce:
1. Create a Filesystem plain/blank PVC 2. Attach it directly to a VM 3. Perform live storage migration
Actual results:
Migration succeeds
Expected results:
Warning or Block that one of the PVC may not be a proper VM disk.