yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #01505
[Bug 1154473] Re: Nova no longer reconnects if libvirt is restarted
** Changed in: nova
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1154473
Title:
Nova no longer reconnects if libvirt is restarted
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
Nova used to recover gracefully if libvirt was restarted out from
under it, this is no longer the case. Steps to reproduce:
1. Start libvirtd (I am using version 1.0.2)
2. Start nova-compute (tested using master branch as of 3/13/2013)
3. Observe that everything functions normally
4. Restart libvirtd
5. nova-compute will now throw exceptions for every subsequent operation (nova.manager libvirtError: internal error client socket is closed)
This is a serious issue, as nova-compute will not recover on its own
without being restarted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1154473/+subscriptions