When a user resizes a VM's disk through the OpenShift Virtualization web console, the underlying PersistentVolumeClaim (PVC) is correctly resized. However, upon restarting the virtual machine we observerd it re-provisions a new PVC based on the old size specified in the dataVolumeTemplate. This new PVC replaces the old one, causing the VM to boot with a smaller, unpopulated disk, resulting in data loss. 

Old detached PVC will remains there on the cluster.

CNV 4.18

100%

1.Create a VM in OpenShift Virtualization 4.18 where the disk is defined using a dataVolumeTemplate
2.Start the VM and add some data to the disk. 
3.Navigate to the VM's disk in the OpenShift console and resize the PVC to a larger size.
4.Observe PVC size through console and CLI.
5. Restart the VM from the console.

1. The console does not reflect the resized PVC.
2. A new PVC with a prefix of dv- and the original size is created.
3. The VM mounts this new, smaller PVC.
4. The data that was added in Step 2 is lost.
5. The original(detached), resized PVC is remains on cluster.

Upon restarting the VM after resizing the disk in the console, the virt-controller should reconcile the existing, resized PVC and use it for the VM. The expected behavior is:

1. The VM should restart and mount the resized PVC.
2. All data on the disk should be preserved.
3. The disk size inside the VM should reflect the new, larger capacity.