Description of problem: UUIDs for VMs are used extensively internally, and often appear in logs and errors. However, determining a particular VM's UUID from the Web UI is harder than it should be. Actual results: Selecting a VM in the Web UI does not show an obvious way to determine its UUID. Given a VM's UUID, neither is there an easy way to find the corresponding VM in the UI. Expected results: The VM's UUID should appear in the General tab when a VM is selected in the UI. Entering a VM's UUID in the Web UI search field should locate the VM with that UUID in the UI.
this is an RFE in fact, though small.
should be in WebAdmin's VM general subtab
merged at: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=f82dc831a1025928207a678337d01e43c1707823
added another patch for searching VM by Id: VMs: Id = xyz...
Search by VM Id merged at: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=52c17b6bb7f3e599f46f03f05d7304a78fdc8a8f
in is13 VM id is visible in general tab, and VM can be filtered out by using the id Search Vms: id =24b04c8b-d2f2-4cc3-a2f1-e9b063476875 lists correct machine verified
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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-2014-0038.html