Description of problem: After upgrading from Fedora 30 to 31, systemd-udevd no longer renames network interfaces. It is always failing with errors such as: Jan 03 09:52:03 d2htg62 systemd-udevd[782]: eno1: Failed to rename network interface 3 from 'eno1' to 'foobar': Device or resource busy Jan 03 09:52:03 d2htg62 systemd-udevd[782]: eno1: Failed to process device, ignoring: Device or resource busy I have tried configuring the renaming by both setting the DEVICE/HWADDR in ifcfg file and using systemd-networkd .link files to do the rename, neither method works. Example .link file: [Match] MACAddress=98:90:96:xx:xx:xx [Link] Name=foobar Version-Release number of selected component (if applicable): systemd-udev-243.5-1.fc31.x86_64 How reproducible: Always occurred on this PC since upgrading, not sure if it affects a clean install. Steps to Reproduce: 1. Configure udev or networkd to rename devices 2. 3. Actual results: Network device not renamed Expected results: Network device is renamed Additional info:
I was experimenting the same issue. In my case, due to an unrelated reason, I omit the systemd, systemd-initrd and dracut-systemd dracut modules (under /etc/dracut.conf.d), and the resulting initramfs was setting up the Ethernet link before even mounting the filesystems, and that's why was reported as busy by udevd. The workaround was to omit also the ifcfg module.
This bug was filed against udev package, but that page is logn gone (and nobody looks at the bugs here). Reassigning to systemd.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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' of '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.