Bug 203769
Summary: | Regression: Valid network link no longer detected | ||
---|---|---|---|
Product: | Networking | Reporter: | Greg White (gwhite) |
Component: | Other | Assignee: | Stephen Hemminger (stephen) |
Status: | NEW --- | ||
Severity: | normal | CC: | anthony.louis.eden, EmilianMedve, Ian.kumlien, kyle.d.pelton, linux, michael, Nicolas.Mailhot, yaneti |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.2.0-rc2 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Greg White
2019-06-01 09:53:51 UTC
I've also noticed this. The commit breaks systemd-networkd with the following error: /usr/lib/systemd/systemd-networkd Enumeration completed ens2: Could not bring up interface: Invalid argument I am running systemd v241 I can confirm the same on Fedora rawhide. Again a systemd-networkd setup. If I manually ip link set up the device it comes up and works. https://bugzilla.redhat.com/show_bug.cgi?id=1718192 has another breakage example, with e1000, alx and bond This is actually a systemd bug: https://github.com/systemd/systemd/issues/12784 Fixed by https://github.com/systemd/systemd/commit/4eb086a38712ea98faf41e075b84555b11b54362 and https://github.com/systemd/systemd/commit/9f6e82e6eb3b6e73d66d00d1d6eee60691fb702f. *** Bug 204099 has been marked as a duplicate of this bug. *** I don't know if this is only systemd:s fault - 5.1.16 works just fine with the same binaries. |