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 #547431 +++
Description of problem:
libvirt allows a user to create two pools with exactly the same underlying storage. The simplest example is two directory pools that point to the same directory, but iSCSI and other pool types behave similarly. The result is that libvirt can have a pool with an inconsistent view of its volumes if the other pool has been used to issue the volume modification operation. For example, if two directory pools point to the same directory, and one pool is used to create a volume, the other pool will remain unaware of the new volume until it is refreshed.
Version-Release number of selected component (if applicable):
libvirt-0.6.3-24
How reproducible:
100%
Steps to Reproduce:
1. Create a directory pool pointing to a given directory
2. Create a second pool pointing to the same directory
Actual results:
Two pools will be created.
Expected results:
The second pool should be rejected.
Additional info:
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as an
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
commit 5a1f2728754a7b7bea4efd245d7171ab6286d681
Author: Lei Li <lilei.ibm.com>
Date: Mon Sep 5 15:52:03 2011 +0800
Check for source conflicts in storage pools
Fix bug #611823 storage driver should prohibit pools with duplicate
underlying storage.
Add internal API virStoragePoolSourceFindDuplicate() to do uniqueness
check based on source location infomation for pool type.
* AUTHORS: add Lei Li
Patch is in upstream.
I can reproduce this bug with libvirt-0.8.7-18.el6_1.3.x86_64
can create two directory pools point to the same directory.
verify on libvirt-0.9.9-1.el6.x86_64
step:
# virsh pool-list --all
Name State Autostart
-----------------------------------------
default active yes
dir active yes
testiqn active yes
# virsh pool-dumpxml dir > dir.xml
# vim dir.xml
change pool name and UUID in xml file,but don't change path
# virsh pool-define dir.xml
error: Failed to define pool from dir.xml
error: operation failed: Storage source conflict with pool: 'dir'
The second pool is rejected.
verification passed.
move 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.
http://rhn.redhat.com/errata/RHSA-2012-0748.html