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
Can't start pool with uuid, and other commands like:net-start uuid, vol-create-as pooluuid xxxx...etc not support use with uuid.

Version
libvirt-0.9.10-21.el6.x86_64

How reproducible:
100%


Steps to Reproduce
0, prepare a pool
1,
virsh # pool-uuid nfs
9401f015-e2cb-2cb2-2c05-83ba92c8cb4b

virsh # pool-name 9401f015-e2cb-2cb2-2c05-83ba92c8cb4b
nfs

virsh # pool-start nfs
Pool nfs started

virsh # pool-destroy nfs
Pool nfs destroyed

virsh # pool-start 9401f015-e2cb-2cb2-2c05-83ba92c8cb4b
error: failed to get pool '9401f015-e2cb-2cb2-2c05-83ba92c8cb4b'
error: Storage pool not found: no pool with matching name '9401f015-e2cb-2cb2-2c05-83ba92c8cb4b'


Actual results：
error: failed to get pool '9401f015-e2cb-2cb2-2c05-83ba92c8cb4b'
error: Storage pool not found: no pool with matching name '9401f015-e2cb-2cb2-2c05-83ba92c8cb4b'


Expected results:
works

Additional info:

commit 68fcfdb8bd33ef323c6c4c5b9a92b1a44829eb6a
Author: Osier Yang <jyang>
Date:   Mon Jun 4 16:37:55 2012 +0800

    virsh: Accept UUID as an argument for net-info and net-start

commit 05f8917f965101d1d2142ff4529aefcebe22aeb2
Author: Osier Yang <jyang>
Date:   Mon Jun 4 16:35:34 2012 +0800

    virsh: Accept UUID as an argument for storage commands
    
    Affected commands are: pool-start, vol-create-from.


Commits are in upstream, move to POST.

Verify this bug with : 
libvirt-0.9.13-3.el6.x86_64

# virsh pool-uuid default
30d11a0d-856b-1931-2998-f32d5a0c1bc9

[root@intel-q9400-4-2 virsh-rail]# virsh pool-destroy 30d11a0d-856b-1931-2998-f32d5a0c1bc9
Pool 30d11a0d-856b-1931-2998-f32d5a0c1bc9 destroyed

[root@intel-q9400-4-2 virsh-rail]# virsh pool-start 30d11a0d-856b-1931-2998-f32d5a0c1bc9
Pool 30d11a0d-856b-1931-2998-f32d5a0c1bc9 started

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-2013-0276.html