[Bug 1455608] Re: upstart job state switched to running before the sock file created

[Edward Hope-Morley]

@smb i'm happy to remove the "waiting on..." as it is just debug fluff
on top of the other two messages that provide enough info on their own.
As for the upstart exit code, i agree it should be 1 not 0, as in the
sysv. I'll get that fixed. Thanks for the review!

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1455608

Title:
  upstart job state switched to running before the sock file created

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Trusty:
  In Progress
Status in libvirt source package in Utopic:
  In Progress
Status in libvirt source package in Vivid:
  In Progress
Status in libvirt source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * Dependent upstart services fail to start because they cannot
  connect to libvirt through the sock file

  [Test Case]

   * This is a race, and can sometimes be hit by stopping libvirt-bin
  and the dependent upstart services, and restarting them again.

  [Regression Potential]

   * None

  Dependent services get kicked off before libvirtd is really ready for
  serving incoming requests - the libvirt-sock sock file hasn't been
  created.

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