-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
network-legacy
module seems to be broken in F31+
#732
Comments
Also, when trying to bisect it I noticed (apart from that it's futile) that on F30 everything worked as expected, but started failing immediately after the Docker image was bumped to F31. |
After comparing the results from F30 and F31 runs, there's something weird going on with the NIC naming: F30 (passing)
F31 (failing)
Notice that on F31 "dracut" tries to use
This could, theoretically, be a race condition, according to the logs from the same F31 machine:
|
Running the VM with
|
network-legacy
seems to be broken in F31+network-legacy
module seems to be broken in F31+
I noticed two additional things:
|
This is fishy!
udevd stated that it will rename the device from 'eth0' to 'ens3' and should set $env{INTERFACE} accordingly in I will try to bisect the systemd-udevd changes. |
This is the offending patch: |
Opened an issue: |
Offending PR: |
The original behavior of $env{INTERFACE} was undocumented and changed in the recent udev versions, breaking the ability to bring up networking reliably. Switching to $name directive should fix this issue. Related links: - systemd/systemd#12700 (udev PR) - systemd/systemd#12291 (related udev issue) - systemd/systemd#14935 (this issue, udev side) - dracutdevs#732 (this issue, dracut side) Fixes: dracutdevs#732
The original behavior of $env{INTERFACE} was undocumented and changed in the recent udev versions, breaking the ability to bring up networking reliably. Switching to $name directive should fix this issue. Related links: - systemd/systemd#12700 (udev PR) - systemd/systemd#12291 (related udev issue) - systemd/systemd#14935 (this issue, udev side) - dracutdevs#732 (this issue, dracut side) Fixes: dracutdevs#732 (cherry picked from commit a8ba1c4)
In attempt to make the dracut's test suite stable & working again, so it could be possibly extended to cover the IPv6 stack as well, I tried to debug the outstanding issues in #731 with following results:
@lnykryn @lkundrak it looks like there's something wrong with the
network-legacy
module, as the majority of network-related test fails was resolved by switching to NetworkManager (network-manager
module). From what I could read from the failing logs, the initrd with legacy network scripts simply fails to obtain a DHCP lease, whereas with NetworkManager everything works as expected.Locally (Fedora 31) in
TEST-20-NFS
I managed to reproduce this as follows:network-legacy
module)network-manager
module)As much as I'd like to stick with NM (where debug logs are actually useful), I suspect this should be looked into as well.
The text was updated successfully, but these errors were encountered: