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.
I can reproduce it on libvirt-0.10.2-32.el6.x86_64
#man virsh
undefine
...........
Volume deletion is only attempted after the domain is undefined; if not
all of the requested volumes could be deleted, the error message
indicates what still remains behind. If a volume path is not found
in the domain definition, it’s treated as if the volume was
successfully deleted. (See domblklist for list of target names
associated to a domain). Example: --storage
vda,/path/to/storage.img
..........
The following line was not found in manual page.
Only volumes managed by libvirt in storage pools can be removed this
way.
I am sorry. Please ignore comment 4.
This bug is fixed in libvirt-0.10.2-32.el6.x86_64
#man virsh
undefine domain
..............
The --storage flag takes a parameter volumes, which is a comma
separated list of volume target names or source paths of storage
volumes to be removed along with the undefined domain. Volumes can
be undefined and thus removed only on inactive domains. Volume
deletion is only attempted after the domain is undefined; if not
all of the requested volumes could be deleted, the error message
indicates what still remains behind. If a volume path is not found
in the domain definition, it’s treated as if the volume was
successfully deleted. *Only volumes managed by libvirt in storage
pools can be removed this way.* (See domblklist for list of target
names associated to a domain). Example: --storage
vda,/path/to/storage.img
....................
The following line was found in manual page.
Only volumes managed by libvirt in storage pools can be removed this
way.
So I change the status 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/RHBA-2014-1374.html
I can reproduce it on libvirt-0.10.2-32.el6.x86_64 #man virsh undefine ........... Volume deletion is only attempted after the domain is undefined; if not all of the requested volumes could be deleted, the error message indicates what still remains behind. If a volume path is not found in the domain definition, it’s treated as if the volume was successfully deleted. (See domblklist for list of target names associated to a domain). Example: --storage vda,/path/to/storage.img .......... The following line was not found in manual page. Only volumes managed by libvirt in storage pools can be removed this way.