Bug 1143955
Summary: | libvirtd crashed after running "virsh metadata --remove" command | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Ruifeng <rbian> | ||||
Component: | libvirt | Assignee: | Erik Skultety <eskultet> | ||||
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.1 | CC: | dyuan, eskultet, mzhan, rbalakri, zhwang, zpeng | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | libvirt-1.2.8-4.el7 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-03-05 07:44:50 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: | |||||||
Attachments: |
|
Description
Ruifeng
2014-09-18 10:18:35 UTC
Fixed upstream: commit 288c47406cffa7a6eb9e9c29764850b0cdeb5508 Author: Erik Skultety <eskultet> Date: Thu Sep 18 14:25:05 2014 +0200 Fix libvirtd crash when removing metadata When trying to remove nonexistent metadata from XML, libvirt daemon crashes due to dereferencing NULL pointer. Resolves https://bugzilla.redhat.com/show_bug.cgi?id=1143955 v1.2.8-197-g288c474 I can reproduct this issue with build: libvirt-1.2.8-2.el7.x86_64 verify with build:libvirt-1.2.8-4.el7.x86_64 step: # ps -ef | grep libvirtd root 15093 1 1 13:52 ? 00:00:00 /usr/sbin/libvirtd root 15119 14076 0 13:53 pts/0 00:00:00 grep --color=auto libvirtd # virsh metadata rhel7 "http://herp.derp" --remove Metadata removed # ps -ef | grep libvirtd root 15093 1 1 13:52 ? 00:00:00 /usr/sbin/libvirtd libvirtd not crash movet to 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/RHSA-2015-0323.html |