Hmm - a tricky race and one I think we have seen with other tools that
use libvirt; I think the latest nova code is a little more intelligent
and will try a few times and mark itself disabled in the event that the
connection can't be established, rather than shutting down.
** Changed in: nova (Ubu
What I believe it's happening here is that libvirt declares itself as
started, but it's not functional yet. Maybe nova-compute should do some
while looping in upstart's pre-start? :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Also affects: nova (Fedora)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382837
Title:
nova-compute is started before libvirt
To manage notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382837
Title:
nova-
