compute agent no longer reconnects if libvirtd is restarted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Medium
|
Guangyu Suo |
Bug Description
The libvirt inspector may can't inspect data from libvirt on some occasions after libvirtd is restarted, though we have reconnecting logic. It happens by chance. The wierd thing is that there is not any exception log when it occurs. The way to reproduce is to restart libvirtd during compute agent polling data. I am using libvirt version 1.2.11 on CentOS 6.5.
After some debuging and reseaching, I found when this occurs, it will raise libvirt.
Also I found there is the same logic in nova/libvirt, and it has fixed this issue two years ago: https:/
The libvirt error code can be found here: https:/
summary: |
- compute agent no longer reconnects if libvirt is restarted + compute agent no longer reconnects if libvirtd is restarted |
Changed in ceilometer: | |
importance: | Undecided → Medium |
Changed in ceilometer: | |
milestone: | none → liberty-rc1 |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | liberty-rc1 → 5.0.0 |
Fix proposed to branch: master /review. openstack. org/225699
Review: https:/