Public bug reported: Description ===========
nova-compute still report service up when libvirtd stop response,and it's fake up state easily make the api request failed. notice, we can see the libvirtd process is running but it have no response to client request. Steps to reproduce ================== it's hard to reproduce the libvirtd death, but it easy to make libvirtd stop response, u can use gdb attach libvirtd process to simulate the issue: gdb -p `pidof libvirtd` Expected result =============== nova-compute should report the down state if encounter libvirtd failed | 9 | nova-compute | zztest04 | nova | disabled | up | 2017-05-31T11:18:58.000000 | AUTO: Connection to libvirt lost: 1 | Actual result ============= nova-compute not sensitive enough and still report state up. | 9 | nova-compute | zztest04 | nova | enabled | up | 2017-05-31T11:18:58.000000 | - | Environment =========== [root@zztest04 nova]# git describe --tags 15.0.0.0rc1-313-g5cf6bbf i think this bug existed widely no matter what nova version is. Reason =========== nova-compute collect libvirtd event through Python libvirt module, and there are no event dispatched to compute eventlet handler when libvirtd dead. please read more from libvirt guide about event handling: http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Events_and_Timers.html ** Affects: nova Importance: Undecided Status: New -- 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/1694584 Title: nova-compute still report service up when libvirtd stop response Status in OpenStack Compute (nova): New Bug description: Description =========== nova-compute still report service up when libvirtd stop response,and it's fake up state easily make the api request failed. notice, we can see the libvirtd process is running but it have no response to client request. Steps to reproduce ================== it's hard to reproduce the libvirtd death, but it easy to make libvirtd stop response, u can use gdb attach libvirtd process to simulate the issue: gdb -p `pidof libvirtd` Expected result =============== nova-compute should report the down state if encounter libvirtd failed | 9 | nova-compute | zztest04 | nova | disabled | up | 2017-05-31T11:18:58.000000 | AUTO: Connection to libvirt lost: 1 | Actual result ============= nova-compute not sensitive enough and still report state up. | 9 | nova-compute | zztest04 | nova | enabled | up | 2017-05-31T11:18:58.000000 | - | Environment =========== [root@zztest04 nova]# git describe --tags 15.0.0.0rc1-313-g5cf6bbf i think this bug existed widely no matter what nova version is. Reason =========== nova-compute collect libvirtd event through Python libvirt module, and there are no event dispatched to compute eventlet handler when libvirtd dead. please read more from libvirt guide about event handling: http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Events_and_Timers.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1694584/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp