[Bug 1567811] Re: nova-compute should depend on libvirt-bin.service instead of libvirtd.service

[ChristianEhrhardt]

I just discussed this with Stefan Bader.
He already had a patch ready when I was cleaning up the git we maintain for Xenial.

In Yakkety we already have the service being libvirtd but with an compat alias to libvirt-bin.
That ensures either names work well in dependencies and eases the transition.

But on Xenial it still is libvirt-bin service. Depending on backports or other unmodified patches this might cause issues by something from Debian depending on libvirtd which wasn't adapted.
To also avoid these issues we add an libvirtd alias to the libvirt-bin service in xenial.

This will allow systemd services which were not modified when merging
from Debian to correctly depend on libvirtd. Also will simplify things
when we finally get rid of the special naming.

Attaching updated Debdiff for an Ack of SMB (the Author) before upload.
While he does so I'll run some tests against it - package to test is building at https://launchpad.net/~paelzer/+archive/ubuntu/qemu-machine-type-dev/+packages.

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

Title:
  nova-compute should depend on libvirt-bin.service instead of
  libvirtd.service

Status in libvirt package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  In Progress

Bug description:
  The service definition in /lib/systemd/system/nova-compute.service
  contains

  After=libvirtd.service

  however that service does not exist, the correct service name would be
  libvirt-bin.service. As a result, nova-compute is started too early
  and fails because it cannot talk to libvirtd after a reboot.

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