vm clone process involves vmsnapshot and vmrestore.
The latter uses the vm spec stored in the vmsnapshot to create a new vm by applying some patches.
If the vm clone requires some label or annotation filtering, the restore generated will apply some `remove` patch command to create the desired target vm spec.
In the clone process, these patches are generated from the running vm spec and not from the vm spec stored in the vmsnapshot.
If some annotations/labels are added to the vm during the clone, and they should be filtered out by the clone filter rules, it can happen that the clone will be stuck in the `RestoreInProgress` status.
This because the restore patches includes some `remove` keys instructions, but these keys are not present in the vm spec stored in the vmsnapshot, but only in the running vm.
This can happen only if a vm clone involves label/annotation filtering and the probability to hit this bug is directly proportional to the delta time between the snapshot and the restore.

4.15

Hard to reproduce, seen this from the u/s check-for-flakes lane

1.
2.
3.