Bug 475276
Summary: | Updating libvirt breaks hypervisor autodetection until libvirtd restart | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Snook <csnook> |
Component: | libvirt | Assignee: | Daniel Veillard <veillard> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | berrange, clalance, crobinso, veillard, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-22 13:19:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Snook
2008-12-08 19:01:36 UTC
Regretably, there is nothing we can do about this particular bug, since it only hits on the upgrade to 0.5.0 - any new release we made now would not be affected. As of the next 0.6.0 release though, it will be possible to restart the libvirtd daemon without killing active VMs, which means we can put a 'service libvirtd restart' in the RPM %post to deal with any such issues like this in the future. |