Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a storage pool with unsupported format type , such as "asdf"
2. check the libvirtd status
3.
Actual results:
# virsh pool-define pool.xml;service libvirtd status
error: Failed to define pool from pool.xml
error: server closed connection:
libvirtd dead but pid file exists
Expected results:
Could tell the format type is not supported , and don't kill libvirtd
Additional info:
Example XML
<pool type='disk'>
<name>sdb</name>
<source>
<device path='/dev/sdb'>
</device>
<format type='auto'/>
</source>
<target>
<path>/dev</path>
<permissions>
<mode>0700</mode>
<owner>0</owner>
<group>0</group>
</permissions>
</target>
</pool>
Verified with libvirt-0.8.7-13.el6.x86_64, it's normal error info provided. Move to VERIFIED.
# rpm -q libvirt qemu-kvm kernel
libvirt-0.8.7-13.el6.x86_64
qemu-kvm-0.12.1.2-2.150.el6.x86_64
kernel-2.6.32-120.el6.x86_64
# virsh pool-define pool.xml
error: Failed to define pool from pool.xml
error: XML description for unknown pool format type XXXX is not well formed or invalid
# service libvirtd status
libvirtd (pid 26317) is running...
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0596.html
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a storage pool with unsupported format type , such as "asdf" 2. check the libvirtd status 3. Actual results: # virsh pool-define pool.xml;service libvirtd status error: Failed to define pool from pool.xml error: server closed connection: libvirtd dead but pid file exists Expected results: Could tell the format type is not supported , and don't kill libvirtd Additional info: Example XML <pool type='disk'> <name>sdb</name> <source> <device path='/dev/sdb'> </device> <format type='auto'/> </source> <target> <path>/dev</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> </target> </pool>