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

[Chris J Arges]

Hello Dr., or anyone else affected,

Accepted libvirt into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.3.1-1ubuntu10.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  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-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-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!

** Changed in: libvirt (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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:
  Fix Committed

Bug description:
  [Impact]

   * libvirt service name was changed from libvirt-bin to libvirtd. Newer 
     releases hold an alias to older libvirt-bin name. But any newer guide, 
     backport to any other package and such might call the new libvirtd 
     name. Yet in the Xenial release we have only the old name being 
     libvirt-bin.

   * This adds an alias libvirtd to Xenials libvirt-bin, to avoid issues in 
     maintenance and backports by matching the newer (and the Debian) name 
     of the service with the alias.

  [Test Case]

   * try to start it as libvirtd service like "service libvirtd status" just 
     as any newer guide and any user (or backport) coming from debian will 
     do.

  [Regression Potential]

   * Just as we want to prevent issues by inserting a service alias to the 
     new (and Debian) name there might be issues being caused by that. While 
     none came up in testing this is still possible.

  [Other Info]
   
   * Yes this is a preemptive fix, but suggested by smb who maintains 
     libvirt for quite a while now and has lived through the pain when 
     things are not fixed preemptively. So I hope this can still be 
     considered as a valid SRU

  -----

  
  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