Red Hat Bugzilla – Bug 1280037
biosdevname naming conventions not applied
Last modified: 2016-12-20 10:38:54 EST
Created attachment 1092399 [details]
sudo udevadm test /sys/class/net/eno1 > udevadm_eno1.txt
Description of problem:
biosdevname rules seem to be ignored after upgrade from F22 to F23.
The NIC on my machine was renamed from em1 to eno1 after the upgrade.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Perform dnf system-upgrade from F22 to F23 with biosdevname installed.
NIC name changed from em1 to eno1
eno1 reverted to the default firewalld zone
firewalld zone configuration for em1 persisted, but was unused
other services stopped working (mediatomb)
NIC name should not change on upgrade
Note that this has security implications, because the firewalld zones are tied to the NIC's name, and the name change can place the NIC in a different zone. Other side-effects can occur in network applications/services which are sensitive to the name change (mediatomb was one I encountered) for availability.
Created attachment 1092400 [details]
sudo udevadm test /sys/class/net/eno1 2> udevadm_eno1-err.txt
I got the same problem, also after dnf upgrade 22 to 23. Except for that my nic now gets the terrible name "enp0s31f6".
But the linked document says biosdevname should take precedence if installed? I have biosdevname installed and the output from 'biosdevname -i enp0s31f6' is 'em1'.
Nah, biosdevname is going away in the future, however naming scheme it provides will stay in one form or another. In the interim it should work if installed.
Removing or re-installing the biosdevname rpm did not change the naming. And the machine is still using old-style network scripts in case it makes any difference.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.