RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 1628578 - No mention of paravirtualized devices naming
Summary: No mention of paravirtualized devices naming
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Networking_Guide
Version: 7.7-Alt
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Marc Muehlfeld
QA Contact: Zhang Kexin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-13 13:22 UTC by Lukas Zapletal
Modified: 2019-05-06 08:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-06 08:54:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Zapletal 2018-09-13 13:22:01 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/ch-consistent_network_device_naming

Section Number and Name: 
CHAPTER 8. CONSISTENT NETWORK DEVICE NAMING

Describe the issue: 
After reading the rules in section 8.1. Naming Schemes Hierarchy it is not clear how paravirtualized network cards will be named.

Suggestions for improvement: 
We should be explicit here. The correct answer is scheme 2 (PCIe card naming convention - ens) but please verify this this is just my wild guess.


Additional information: 
In RHEL7 consitent naming for virtio-net driver must be explicitly enabled: https://access.redhat.com/solutions/3219091

Comment 8 Lukáš Nykrýn 2019-05-06 08:51:29 UTC
But to be honest, I don't think we should change the doc here. It does not matter if the device is virtualized or not, the rules are still the same. And the net.ifnames=1 is just an ugly hack. Maybe it is fine if it is just documented in the KB.


Note You need to log in before you can comment on or make changes to this bug.