Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1535009

Summary: [UI] - Provide indication in the ui what is the vdsm name of the logical name
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.1.1CC: bugs, dholler, michal.skrivanek
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 4.3.0-0.2.master.20181203100035.git0ee44c1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:46:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Burman 2018-01-16 13:07:08 UTC 
Description of problem:
[UI] - Provide indication in the ui what is the vdsm name of the logical name.

We must get indication in some way(tooltip, column, general info sub tab...) about the vdsm name of the logical name. If creating long name network, vdsm generates vdsm name with 'onuuid' prefix, we must get this indication in the ui in order to use the custom physnet feature, without the need to ssh to the host.

Version-Release number of selected component (if applicable):
4.2.1.1-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1. Create network with 16 characters
2. Attach the network to the host
3. Try to figure out the vdsm name of this network without ssh to the host

Actual results:
No indication in the ui for vdsm name<>logical name

Expected results:
We must have such info in the ui. 

Additional info:
This should have been part of the long name RFE
Comment 1 Michael Burman 2018-01-17 07:35:15 UTC 
You are right, by mistake
Comment 2 Michael Burman 2018-11-30 09:38:34 UTC 
I don't see the fix on 4.3.0-0.5.alpha1.el7
Comment 3 Dominik Holler 2018-11-30 09:47:21 UTC 
4.3.0-0.5.alpha1.el7 is on oVirt Engine 2451c36170b950202df1073f3838bb465a5152b6, which does not contain the relevant 0ab52a10f776219f7da352f1c47ab2b0b317b09c.
Comment 4 Michael Burman 2018-12-05 07:58:37 UTC 
Verified on - 4.3.0-0.2.master.20181203100035.git0ee44c1.el7

VDSM Name:    on59bbd21b6c9c4
Comment 5 Sandro Bonazzola 2019-02-13 07:46:42 UTC 
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.