Created attachment 918410 [details]
vdsm and engine logs
Description of problem:
1 vm with OS.
Creating new file on vm and suspend it. When in suspend state, take snapshot.
After snapshot operation complete, delete the file and preview.
The expected result is that the file will be found on the vm's disk.
The file is not fount in the vm's disk
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. explained above
The file should be restore after previewing the snapshot
Raz, how is it an automation blocker?
It should be Regression not automation blocker.
I have a hard time finding anything in the noise of vdsm. Would it be possible to retry, as there are several issues in the log already addressed in recent 3.5 builds
Created attachment 927420 [details]
vdsm and engine logs
still quite a noise…which version did you use for comment #4?
I don't see any issues so far
decreasing severity as easy workaround exists
What do you expect to see?
I wrote in the description that the issue is that the file that was part of the isn't restored after we delete the file and and preview.
In logs all is good.
So I think the severity should be urgent since this basic operation could cause a data loss
Ok thanks to Raz i got this reproduced,
i think we already seen a similar issue before,
the problem is that when resuming from hibernation, vdsm is using the saved configuration file to start the vm, in this file, the volume id is the previous snapshot volume, and vdsm ignore the new snapshot volume id sent from the engine.
this means that the vm is still using the previous snapshot, and only after fresh restart the vm will use the new snapshot.
not sure if we need to fix vdsm to handle this situation, or just decide to block snapshot for suspended vm
also, i dont think this is a regression, Raz, did this flow ever worked?
According to previous test runs it used to work
removing regression flag, i verified the same behaviour in 3.4
please let me know if you are able to see this working on previous version.
since we dont have hibernation information saved in the snapshot (ovf) i am in favor of blocking snapshot for suspended vm.
Michal what do you think?
(In reply to Omer Frenkel from comment #9)
Engine RHEVM: 3.6.0-0.13.master.el6
1. Create VM with OS
2. Run VM
3. Suspend VM
4. Take snapshot on this VM
Operation canceled with message:
"Cannot create Snapshot because the VM is in Suspended status"
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.