Bug 1331700

Summary: Virtual NIC incorrectly labeled as physical
Product: Red Hat Satellite Reporter: Maxim Burgerhout <mburgerh>
Component: Compute ResourcesAssignee: Marek Hulan <mhulan>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, dcaplan
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-08 09:05:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Interface configuration showing 'virtual (NAT)"
none
NIC is listed as attached to physical network none

Description Maxim Burgerhout 2016-04-29 10:06:20 UTC
Created attachment 1152204 [details]
Interface configuration showing 'virtual (NAT)"

Description of problem:
On the new network configuration page, a NIC is always labeled as physical, even though it's a virtual interface. See screenshots.

Version-Release number of selected component (if applicable):
6.2.0 beta

How reproducible:


Steps to Reproduce:
1. Create new machine on virtual provider, like libvirt
2. Go to Interfaces tab
3.

Actual results:
You'll see physical@NAT, no matter what

Expected results:
Should show Virtual@NAT

Additional info:

Comment 1 Maxim Burgerhout 2016-04-29 10:08:29 UTC
Created attachment 1152205 [details]
NIC is listed as attached to physical network

Comment 2 Maxim Burgerhout 2016-04-29 10:09:20 UTC
Just realized this 'virtual' and 'physical' labeling could also mean the type of network _interface, but then it's quite ambiguous

Comment 3 Marek Hulan 2016-06-08 06:55:43 UTC
Please note that the physical interface means a physical in terms of OS, virtual is for logical device like bond, vlan, alias, bridge. On libvirt the interface is virtual since it's running in VM but for the VM itself, it's physical device as well as CPU, RAM etc. The fact that it's emulated interface should be observable by the '@$something' notation. I agree that it might be slightly confusing, but I'd like to avoid long strings in that column.

If you come up with a better string or indicator which keeps the information about whether it's NAT or bridge and which one is used (there may be more NATs and bridges) then I'm happy to change it. Note that the similar notation should work for other compute resources as well. Otherwise I'd recommend to stick with what we have now.

Comment 4 RHEL Program Management 2016-06-08 09:05:35 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.