Bug 1176510
| Summary: | Volumes list duplicates after libvirtd reloading | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Hao Liu <hliu> |
| Component: | libvirt | Assignee: | John Ferlan <jferlan> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | dyuan, hliu, jferlan, lhuang, mzhan, rbalakri, xuzhang, yanyang |
| Target Milestone: | rc | ||
| Target Release: | 7.2 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-1.2.13-1.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 06:05:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Hao Liu
2014-12-22 07:57:15 UTC
Seems the reload path (e.g. storageDriverAutostart) doesn't make the virStoragePoolObjClearVols call prior to backend->refreshPool Using 'restart' instead of 'reload' does the right thing. Pushed upstream, moving to POST, wait for libvirt rebase for 7.2 $ git describe 1d2e4d8ca2ae84b5ac5bc63c36d3f75afaac136d v1.2.12-65-g1d2e4d8 $ Verified on libvirt-1.2.14-1.el7.x86_64 Steps: # virsh vol-list HostVG Name Path ------------------------------------------------------------------------------ vol1 /dev/HostVG/vol1 vol2 /dev/HostVG/vol2 vol3 /dev/HostVG/vol3 # systemctl reload libvirtd # virsh vol-list HostVG Name Path ------------------------------------------------------------------------------ vol1 /dev/HostVG/vol1 vol2 /dev/HostVG/vol2 vol3 /dev/HostVG/vol3 According to comment #3, mark it as verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2202.html |