Bug 803600
| Summary: | virt-manager crash when deleting volumes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Stanislav Graf <sgraf> | ||||||||
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 6.2 | CC: | acathrow, dallan, dyasny, hjiang, mzhan, rwu, syeghiay, yupzhang, zpeng | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:c4018b63d6010526b20a39e7026427efc238d1b4 | ||||||||||
| Fixed In Version: | virt-manager-0.9.0-12.el6 | Doc Type: | Bug Fix | ||||||||
| Doc Text: |
Previously, virt-manager could crash if the user quickly deleted several storage volumes in succession. This crash was caused by data locking when deleting the storage volume. This crash has been fixed.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-06-20 12:39:36 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Stanislav Graf
2012-03-15 08:28:20 UTC
Created attachment 570204 [details]
File: backtrace
Created attachment 570205 [details]
File: maps
Libvirt crash, reassigning Hi Stanislav, do you have the core dump file for this crash or are you able to reproduce this? Peter Hi, I was able to reproduce again right now (tried second time, crashed second time, so far 100% reproducibility), abrt has collected all necessary files. Reproduction: - I used virt-manager - logged into local connection (local libvirt) - menu-edit-'connection details' - storage - New volume (default 1000MB) - repeat 10x - test1...test10 - close/exit virt-manager - open virt-manager - logged into local connection (local libvirt) - menu-edit-'connection details' - storage - select volume - 'delete volume' - yes - repeat 10x virt-manager crashed, coredump created Abrt created Bug 809435 using reproduction scenario from Comment 6 This is actualy not a libvirt bug. ABRT is wrongly reporting the crash function to be write() from libvirt's virNetSocketWriteWire() but the backtrace states that the bug happened in function: #0 0x0000003666c52dd3 in node_get_last (iter=<value optimized out>) at gsequence.c:1377 and the libvirt library was just handling a call at that moment. Backtrace to BZ #809435 confirms this. Reassigning back to virt-manager, but it's probably a bug of pygtk. I'm not able to crash the current upstream virt-manager using the procedure in comment 6, so it's probably fixed or worked around. *** Bug 809435 has been marked as a duplicate of this bug. *** Created attachment 577781 [details]
Fix the crash
Sorry for the run around, this is a virt-manager threads issue. Attached patch fixes it for me (and is also what upstream has)
Fix built in virt-manager-0.9.0-12.el6 Reproduced it with virt-manager-0.9.0-11.el6.x86_64 Verified it with the following packages: virt-manager-0.9.0-12.el6.x86_64 qemu-kvm-0.12.1.2-2.286.el6.x86_64 python-virtinst-0.600.0-8.el6.noarch libvirt-0.9.10-14.el6.x86_64 Steps: - Used virt-manager - logged into local connection (local libvirt) - menu-edit-'connection details' - storage - New volume (default 1000MB) - repeat 10x - test1...test10 - close/exit virt-manager - open virt-manager - logged into local connection (local libvirt) - menu-edit-'connection details' - storage - select volume - 'delete volume' - yes - repeat 10x virt-manager is OK. So, move the status to 'verified'.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Previously, virt-manager could crash if the user quickly deleted several storage volumes in succession. This crash was caused by data locking when deleting the storage volume. This crash has been fixed.
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. http://rhn.redhat.com/errata/RHBA-2012-0785.html |