-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
2.9.0
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
MTV Sprint 3, MTV Sprint 4
Description of problem:
Migrate a VM with tpm device from OCP to OCP cluster, the tpm persistent-state pvc is changed after migration
Version-Release number of selected component (if applicable):
MTV 2.9.0 (forklift-fbc-prod-v419:on-pr-9bb01b910a145d7c52259305c88643c394017c8b) with CNV 4.19.1
How reproducible:
Always
Steps to Reproduce:
1) Warm migrate VM: mtv-func-rhel9-uefi (1 disk, 1 nic with dhcp, tpm device) from vCenter 8 to OCP 4.18, the plan executed successfully, there is pvc: persistent-state-for-mtv-func-rhel9-uefi-t7g6s with storage class: ocs-storagecluster-ceph-rbd-virtualization
$ oc get pvc|grep mtv-func-rhel9-uefi
persistent-state-for-mtv-func-rhel9-uefi-t7g6s Bound pvc-f358c6a8-d506-48d3-8436-6806f4f7a699 11Mi RWO ocs-storagecluster-ceph-rbd-virtualization <unset> 4m4s
$ oc get pvc|grep warm-rhel9-tpm
warm-rhel9-tpm-vm-138-vgq92 Bound pvc-e818c934-60f6-436e-8aad-3296b14d6d17 18179755751 RWX nfs-csi <unset> 25m
2) Migrate VM: mtv-func-rhel9-uefi with tpm device from CNV 4.18.9 to CNV 4.19.1, the plan executed successfully, the VM is keep on starting status
3) Check the VM with 2 PVCs: 1 pvc for disk with nfs-csi storage class, 1 pvc is persistent state pvc with ocs-storagecluster-ceph-rbd-virtualization storage class
$ oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE ocp-test-tpm-ecae235c-84b8-4453-a9fe-3dd9a31b2af9-hl8d5 Bound pvc-734a224a-0c6d-4e65-95a9-39209f82dab8 11Mi RWX ocs-storagecluster-ceph-rbd-virtualization <unset> 17m ocp-test-tpm-ecae235c-84b8-4453-a9fe-3dd9a31b2af9-tfgnm Bound pvc-ce679f3e-3df7-4094-bb22-01a242e67e77 19238318189 RWX nfs-csi <unset> 17m
4) Describe VM, it with 1 disk, and with tpm device, and with message: "No default storage class found", more details in attached file: mtv-func-rhel9-uefi-describe
5) set the default storage class: nfs-csi, a new PVC is created by CNV for persistent state tpm device
6) Check the VM is running, with tpm device, check the virt-launcher pod, it's using the new created persistent-state-for-mtv-func-rhel9-uefi-lkwzm for tpm device, more details in attached file: virt-launcher-mtv-func-rhel9-uefi-tjgmc-describe
Actual results:
In step2-6: CNV create another persistent-state pvc for VM after migration
Expected results:
In step2-6: Use original persistent-state pvc for VM after migration
