Bug 1516283
Summary: | Netdev names for nfp driver inconsistent | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Gutter (Netronome) <jan.gutter> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.5 | CC: | bbreard, fsumsal, jiji, kzhang, qding, rkhan, sukulkar, systemd-maint-list, yuma |
Target Milestone: | beta | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | systemd-219-52.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 11:24:09 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: | |||
Bug Depends On: | 1525606 | ||
Bug Blocks: |
Description
Jan Gutter (Netronome)
2017-11-22 12:15:21 UTC
I presume this drivers could be already used in production. If so then we can change the naming scheme since it would change the device names on already existing cards and that is something we just can't do, even the new names would be much prettier. All I can afford is that we can put together a Knowledge Base article, where we will describe how you can add the rule yourself. I'll attempt to find out if there's any customers currently using the in-kernel driver in 7.4 in production. Our out-of-tree driver packages have been shipping udev rules similar to the above, resulting in consistent naming. The problem is also exacerbated because the in-tree driver in 7.4 has no way to distinguish between the netdevs in breakout mode (so the netdev names are actually randomized each boot). The reason for this proposal is because the 7.5 kernel introduces a number of new backported features, meaning that users will expect added functionality. I understand completely if this avenue is not available: automated systems are not smart enough to figure out which fixes break functionality and which do not. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0711 |