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:
RFE: Improve for VM selecting when vm's name is also a meaningful ID or UUID
Version-Release number of selected component (if applicable):
virt-viewer-2.0-12.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a running guest and check it's ID by "virsh list"
# virsh list
Id Name State
----------------------------------------------------
3 rhel7.3-1005 running
4 rhel7.2 running
5 3 running
2. Created a guest which the name is same as a ID of another guest.
3. Run virt-viewer to open the new created guest.
$ virt-viewer -c qemu:///system 3
Actual results:
rhel7.3-1005 is opened.
Expected results:
Due to "3" could be a ID of another guest and the name of a guest, It's better to find all available guest which corresponding to the name/id/uuid the user typed in command line, and show them in a dialog to ask user to select which one is they wanted.
Additional info:
uuid may have same problem when a guest's name is a uuid.
I think it is quite unusual to name a VM name to a id.
Anyways we should better document how the selection process works or maybe add some cmdline option to specify if the VM is specified by name/id/uid.
So adding a new (optional) option to be able to specifically tell virt-viewer it is connecting to a VM-name, VM-ID or VM-UUID, e.g. for your usecase:
$ virt-viewer -c qemu:///system 3
Would still connect to id=3 (being rhel7.3-1005)
$ virt-viewer --vm-name -c qemu:///system 3
would then connect to the VM with name "3".
Sounds more feasible to me, as it would not break automation scripts for opening VM consoles without the possibility of doing user interaction.
I agree with Martin. The situation described in the comment 0 is interesting but it is a corner case.
cli options like --name, --id, --uuid (i would omit the 'vm' to match similar options in other virt tools)
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.
https://access.redhat.com/errata/RHBA-2017:1849