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.
+++ This bug was initially created as a clone of Bug #1025230 +++
Description of problem:
libvirt activate pool with invalid source.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 7.0 Beta
libvirt-1.1.1-10.el7.x86_64
How reproducible:
always
Command:
1. Define a pool with an invalid source.
# cat test_pool.xml
<pool type='fs'>
<name>test_pool</name>
<source>
<device path='/dev/notexist'/>
<format type='ext3'/>
</source>
<target>
<path>/mnt</path>
<permissions>
<mode>0777</mode>
<owner>0</owner>
<group>0</group>
</permissions>
</target>
</pool>
# virsh pool-define test_pool.xml
2. Try to start the pool.
# virsh pool-start test_pool
error: Failed to start pool test_pool
error: internal error: Child process (/usr/bin/mount -t ext3 /dev/notexist /mnt) unexpected exit status 32: mount: special device /dev/notexist does not exist
# virsh pool-list --all
Name State Autostart
-----------------------------------------
default active yes
test_pool inactive no
3. Mount a valid fs to target path.
# mount /dev/sda1 /mnt
4. Restart libvirt daemon.
# service libvirtd restart
5. The invalid pool is active.
# virsh pool-list --all
Name State Autostart
-----------------------------------------
default active yes
test_pool active no
Expected result:
The pool with invalid source should be checked and not be activated when starting libvirt daemon.
Comment 3RHEL Program Management
2014-04-04 20:56:34 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.