[Bug 1329254] [NEW] A VM does not become inactive during the reboot on saucy and later hosts

[Parameswaran Sivatharman]

Public bug reported:

On raring and prior hosts, VMs become inactive at one point during the
first reboot after the installation But starting from saucy as host VMs
do not become inactive during the reboot of preseeded installations but
they do during the reboot after a manual installation.

Basically, the attached script (temp.py) exits during a manual utopic
dekstop installation on a trusty host but continues to loop during the
first reboot for a preseeded install  .

i.e. libvirt.open("qemu:///system").lookupByName("desktop").isActive()
becomes 0 at one point during the reboot after a manual install but not
after a preseeded installation.

This is causing issues like:
https://bugs.launchpad.net/utah/+bug/1199349

in the smoke tests.

I'm not entirely sure if this is really a bug, but this certainly is a
change in behaviour in libvirt since saucy.

** Affects: libvirt (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "temp.py"
   https://bugs.launchpad.net/bugs/1329254/+attachment/4130223/+files/temp.py

** Description changed:

  On raring and prior hosts, VMs become inactive at one point during the
  first reboot after the installation But starting from saucy as host VMs
  do not become inactive during the reboot of preseeded installations but
  they do during the reboot after a manual installation.
  
  Basically, the attached script (temp.py) exits during a manual utopic
  dekstop installation on a trusty host but continues to loop during the
  first reboot for a preseeded install  .
  
  i.e. libvirt.open("qemu:///system").lookupByName("desktop").isActive()
  becomes 0 at one point during the reboot after a manual install but not
  after a preseeded installation.
  
  This is causing issues like:
  https://bugs.launchpad.net/utah/+bug/1199349
  
  in the smoke tests.
+ 
+ I'm not entirely sure if this is really a bug, but this certainly is a
+ change in behaviour in libvirt since saucy.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1329254

Title:
  A VM does not become inactive during the reboot on saucy  and later
  hosts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1329254/+subscriptions