[Bug 1720397] Re: qemu-kvm doesnt restart after node reboot

[Corey Bryant]

Hello Ernie, or anyone else affected,

Accepted qemu into pike-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:pike-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-pike-needed to verification-pike-done. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-pike-failed. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Also affects: cloud-archive/ocata
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/pike
   Importance: Undecided
       Status: New

** Changed in: cloud-archive/ocata
       Status: New => Triaged

** Changed in: cloud-archive/pike
       Status: New => Triaged

** Changed in: cloud-archive/ocata
   Importance: Undecided => High

** Changed in: cloud-archive/pike
   Importance: Undecided => High

** Changed in: cloud-archive/pike
       Status: Triaged => Fix Committed

** Tags added: verification-pike-needed

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1720397

Title:
  qemu-kvm doesnt restart after node reboot

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive ocata series:
  Fix Committed
Status in Ubuntu Cloud Archive pike series:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Zesty:
  Fix Committed
Status in qemu source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Since the Zesty Merge the qemu-kvm service fails to be active by 
     default.

   * It is a non required but rather useful helper, so it should be fixed to 
     be enabled as it was pre zesty due to systemd-generators taking it from 
     sysv scripts back then.

  [Test Case]

   * Install qemu-system-common
   * Then check
     $ systemctl status qemu-kvm
   * This should be active (exited) but is currently disabled

  [Regression Potential]

   * If this script causes any issue for someone (not known so far) and he 
     was running on zesty a while it will on the SRU update be enabled and 
     trigger these issues. Yet this is a generic argument and if that would 
     be a blocker no services would be allowed to be enabled. I verified 
     that if masked the service stays off as it should.

  [Other Info]
   
   * IMO this issue qualified for  (2) the following of the Final Freeze:
     2) Bug fixes that would be suitable for post-release SRUs, which we
     may choose to accept, reject, or shunt to -updates for 0-day SRUs
     on a case-by-base basis.

  --

  
  Upon a MAAS reboot openstack nova-compute services come up blocked with the following message in juju status:

  Services not running that should be: qemu-kvm

  services qemu-kvm status shows the services as dead
  services qemu-kvm restart fixes issue.

  ubuntu at fair-dingo:~$ service qemu-kvm status
  ● qemu-kvm.service - QEMU KVM preparation - module, ksm, hugepages
     Loaded: loaded (/lib/systemd/system/qemu-kvm.service; disabled; vendor preset: enabled)
     Active: active (exited) since Thu 2017-09-28 19:54:17 UTC; 3min 20s ago
    Process: 33714 ExecStart=/usr/share/qemu/init/qemu-kvm-init start (code=exited, status=0/SUCCESS)
   Main PID: 33714 (code=exited, status=0/SUCCESS)

  Linux MaaS 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  Juju 2.2.4-xenial-amd64

  openstack 3.12.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1720397/+subscriptions