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

ChristianEhrhardt 1720397 at bugs.launchpad.net
Tue Oct 17 06:49:02 UTC 2017


Hi Michael,
yeah manually enabling it is a workaround, but to let the maintainer scrtipts do it right on install is still the preferred way to do it.

But all looks good on the way to get it into artful, regression tests, dep8 tests, ...
Might just be blocked a bit by the release week freeze, but other than that the right fix is on its way.

-- 
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:
  New
Status in qemu package in Ubuntu:
  In Progress
Status in qemu source package in Zesty:
  Confirmed
Status in qemu source package in Artful:
  In Progress

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



More information about the Ubuntu-openstack-bugs mailing list