Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionMaxim 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:
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 4RHEL 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.
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: