Description of problem:

Deployed OPENSHIFT VIRTUALIZATION + ODF (internal mode) + HyperShift, created a managed control plane and used VIRT as worker nodes.

It is currently found that after creating a PV on the managed cluster, the dynamically bound storage cannot be found when the node where the PV is located is restarted via the OCP-V UI.

Version-Release number of selected component (if applicable):

OPENSHIFT version 4.16.23

How reproducible:
Steps to Reproduce:
1. Create a PV on the managed cluster, and attach to a pod
2. Reboot the worker node where is the pod located in the OCP-V UI
3. We can see the corresponding virt-launcher-xxxx pod is restarted

Actual results:
The pod failed to start due to the missing storage
Couldn't find the storage information in the virtualmachineinstance and the corresponding virt-launcher-xxxx pod

Expected results:
The storage can be persistent after VM's rebooting

Additional info:

The issue doesn't happen when running reboot in the VM

Similar issues found below:

https://github.com/kubevirt/kubevirt/issues/6010 https://github.com/kubevirt/kubevirt/pull/6079/commits https://github.com/kubevirt/kubevirt/pull/6079/files
https://issues.redhat.com/browse/CNV-50957