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

Bug 1636768

Summary: [UI] - VM - Network Interfaces sub tab - Add <Empty> or [N/A] to the General info for an empty vNIC profile
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.6.2CC: bugs, dholler
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
dholler: devel_ack+
Target Release: 4.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:48:10 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:
Attachments:
Description Flags
screenshot none

Description Michael Burman 2018-10-07 14:17:26 UTC
Created attachment 1491338 [details]
screenshot

Description of problem:
[UI] - VM - Network Interfaces sub tab - Add <Empty> or [N/A] to the General  info for an empty vNIC profile.

Currently if setting an empty vNIC profile for VM's network interface, on the 'General' sub tab the 'Network Name' and 'Profile Name' are just blank white and it's bit confusing, like no data for this interface. 
For an empty vNIC profile we need to add <Empty> or [N/A] in the General sub tab for 'Network Name' and 'Profile Name' instead of blank white.

Version-Release number of selected component (if applicable):
4.2.7.3-0.0.master.20181007094930.git02c1da0.el7

How reproducible:
100%

Steps to Reproduce:
1. Add vNIC to VM with an empty profile

Actual results:
In general info the network and profile names are blank white

Expected results:
In general info the network name and profile are <Empty> or [N/A]

Comment 1 Michael Burman 2018-10-22 07:00:43 UTC
Verified on - 4.3.0-0.0.master.20181016132820.gite60d148.el7

Comment 2 Sandro Bonazzola 2018-11-02 14:34:22 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 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.

Comment 3 Sandro Bonazzola 2018-11-02 14:41:22 UTC
Closed by mistake, moving back to qa -> verified

Comment 4 Sandro Bonazzola 2019-02-13 07:48:10 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.