-
Bug
-
Resolution: Unresolved
-
Normal
-
CNV v4.18.0
-
None
Description of problem:
VM runStrategy was 'RerunOnFailure' or 'Manual', After we create and restore a snapshot - VM runStrategy becomes 'Halted' (for Stopped VM) and 'Always' (for Running VM)
Version-Release number of selected component (if applicable):
4.18 and earlier
How reproducible:
Always
Steps to Reproduce:
1. Create a VM with runStrategy 'RerunOnFailure' 2. Create a VMSnapshot, create a VMRestore 3. See that restored VM has runStrategy 'Halted' 4. Start the VM - VM has runStrategy 'Always'
Actual results:
$ oc get vm -A NAMESPACE NAME AGE STATUS READY snapshots-test-snapshots vm-cnv-5048-1735733610-821901 10m Stopped False $ oc get vm -n snapshots-test-snapshots vm-cnv-5048-1735733610-821901 -oyaml | grep runStrategy runStrategy: RerunOnFailure runStrategy: RerunOnFailure $ oc create -f restore.yaml virtualmachinerestore.snapshot.kubevirt.io/restore-larry-offline created $ oc get vm -A NAMESPACE NAME AGE STATUS READY snapshots-test-snapshots vm-cnv-5048-1735733610-821901 11m Stopped False $ oc get dv -n snapshots-test-snapshots NAME PHASE PROGRESS RESTARTS AGE restore-7c053a9d-c4f7-4c67-a098-50c2155be1eb-dv-disk Succeeded N/A 13s $ oc get vm -n snapshots-test-snapshots vm-cnv-5048-1735733610-821901 -oyaml | grep runStrategy runStrategy: Halted runStrategy: Halted $ virtctl start -n snapshots-test-snapshots vm-cnv-5048-1735733610-821901 VM vm-cnv-5048-1735733610-821901 was scheduled to start $ oc get vm -A NAMESPACE NAME AGE STATUS READY snapshots-test-snapshots vm-cnv-5048-1735733610-821901 13m Running True $ oc get vm -n snapshots-test-snapshots vm-cnv-5048-1735733610-821901 -oyaml | grep runStrategy runStrategy: Always runStrategy: Always
Expected results:
Run strategy stays as it was before the restore
Additional info:
