Created attachment 1114733 [details] engine_log_1 Description of problem: After upgrade engine from 3.5.7 to 3.6.2 suspended VM failed to resume, it when down and up again. Version-Release number of selected component (if applicable): engine 3.5: 3.5.7-0.1.el6ev engine 3.6: 3.6.2-0.1.el6 Setup: DC 3.5 with cluster 3.5 2 host 7.1 in cluster. Steps to Reproduce: 1. Create VM and start it on Host_1 2. Suspend VM 3. Upgrade Host_2 and Host_1 to 7.2 4. Upgrade Cluster level to 3.6 4. Start VM Actual results: VM is down, and restart again. Expected results: VM should run and not got down Additional info: I see the error: VM vm_71-2 is down with error. Exit message: Wake up from hibernation failed:internal error: cannot parse json {"return": , "id": "libvirt-99"}: parse error: unallowed token at this point in JSON text {"return": , "id": "libvirt-99"} (right here) ------^
Created attachment 1114734 [details] engine_log_2
Israel, not sure but I think we'll need VDSM logs as well - please attach them.
Created attachment 1114816 [details] vdsm_log
(In reply to Israel Pinto from comment #3) > Created attachment 1114816 [details] > vdsm_log Thanks - much more helpful (though I could use third of it, no need for such a big log). If libvirt is in debug mode, then libvirt logs would be great too.
Created attachment 1114820 [details] vm_qemu_log
(In reply to Yaniv Kaul from comment #4) > (In reply to Israel Pinto from comment #3) > > Created attachment 1114816 [details] > > vdsm_log > > Thanks - much more helpful (though I could use third of it, no need for such > a big log). If libvirt is in debug mode, then libvirt logs would be great > too. it not in debug hope it can help to :)
this is not planned to be supported. Suspended 3.5 VMs can't be resumed in 3.6 compatibility level. That's what the "compatibility level" means. Suspended VMs cannot be "upgraded" without losing their state, hence a forced Power Off is the only option changing the scope of the bug to: warn on cluster change block resuming VM when compatibility level differs (careful - as master supports a custom one)
actually, just the warning. The blocking is tracked under bug 1292398
Changing title since the actual blocking of the resume is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1292398
Verify: engine 3.5: 3.5.7-0.1.el6ev engine 3.6: 3.6.3.2-0.1.el6 Scenario: 1. Create VM and start it on Host_1 2. Suspend VM 3. Upgrade engine to 3.6 4. Update VM cluster to 3.6 Actual results as expected: New window is opened with the content: "Ti tel: Operation canceled Error while executing action: Cannot update a VM in this status. Try stopping the VM first." PASS