Many tier-1 tests are doing VolumeSnapshot based cloning. When running the sig-storage tests on GCP cluster with 4.18.0, we found an issue in the clone populator VolumeSnapshots watch. If the snapshot wasn't Ready at the initial loop, it won't be re-queued. This is causing DataVolumes to get stuck in the CloneFromSnapshotSourceInProgress phase. It seems that in GCP it takes longer for VolumeSnapshots to become Ready, which revealed this issue.

CNV 4.18.0

Run any snapshot-based cloning tier-1 test on GCP cluster, where VolumeSnaphot is cloned right after its creation, e.g:
sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system] DataVolume clone permission checking using Alpine import/clone should resolve DataVolume sourceRef with Snapshot source

DataVolume will get stuck in the CloneFromSnapshotSourceInProgress phase and never get to Succeeded, and VMs will not get to Ready.

DataVolume clone should continue when VolumeSnaphot becomes Ready, until DataVolume is Succeeded.