Red Hat Bugzilla – Bug 1258349
[libvirt] incorrect XML restore on dehibernation path
Last modified: 2016-02-10 14:23:21 EST
Description of problem:
libvirt 1.2.8 up until 1.2.8-16.el7_1.4 (found in CentOS 7.1) has a bug which causes incorrect XML reload when virDomainRestore is called. We use this API in the restore (dehibernation) flow, so we must make sure we depend on fixed libvirt.
Please note the bug is fixed already upstream, libvirt 1.2.13 (in CentOS 7.2) works fine
100% on CentOS 7.1 with libvirt < el7_1.4
Steps to Reproduce:
1. suspend VM
2. resume VM
3. check the XML of the resumed VM
some fields missing or unexpectedly changed
no unwanted changes
No code change needed on VDSM
waiting for package availability.
(In reply to Francesco Romani from comment #1)
> waiting for package availability.
Package available on CentOS 7.1 since this morning:
[root@goji ~]# rpm -qa | grep libvirt
What is the status of this bug?
Can you please set TM\target if this needs to be ON_QA?
Are the flags correct?
(In reply to Yaniv Dary from comment #3)
> What is the status of this bug?
> Can you please set TM\target if this needs to be ON_QA?
> Are the flags correct?
It needs to be in 3.5.5 (fixed in version 4.16.27) and in 3.6.0 (fixed in version 4.17.7) Targeting 3.5.5.
Please note that we are just consuming a fix from libvirt, hence the amount of testing needed is really minimal.
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Verified on both rhevm 3.5.5 and 3.6:
1. engine: rhevm-3.5.5-0.1.el6ev.noarch
[root@host~]# rpm -qa | grep libvirt
[root@localhost ~]# rpm -qa | grep libvirt
In both cases xmldump of vm is the same before and after suspend and resume, no problem opening a console to the vm via webadmin or ticketing the vm.
(In reply to Red Hat Bugzilla Rules Engine from comment #6)
> Bug tickets that are moved to testing must have target release set to make
> sure tester knows what to test. Please set the correct target release before
> moving to ON_QA.
this bug was already verified as per comment 7. Furthermore, I can't see any 4.16.x relase in the "target release" dropdown menu.
oVirt 3.5.5 has been released including fixes for this issue.