http://bugzilla.opensuse.org/show_bug.cgi?id=1132774 http://bugzilla.opensuse.org/show_bug.cgi?id=1132774#c2 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Network --- Comment #2 from Guillaume GARDET --- As a workaround, I need to: systemctl restart wickedd wicked ifup enp2s0 Apparently 'wickedd' is killed on boot (and then 'wickedd-nanny' fails): ● wickedd.service - wicked network management service daemon Loaded: loaded (/usr/lib/systemd/system/wickedd.service; indirect; vendor preset: disabled) Active: failed (Result: timeout) since Wed 2019-04-17 17:22:10 CEST; 1min 1s ago Apr 17 17:20:40 SoftironGGA systemd[1]: Starting wicked network management service daemon... Apr 17 17:22:10 SoftironGGA systemd[1]: wickedd.service: Start-pre operation timed out. Terminating. Apr 17 17:22:10 SoftironGGA systemd[1]: wickedd.service: Control process exited, code=killed, status=15/TERM Apr 17 17:22:10 SoftironGGA systemd[1]: wickedd.service: Failed with result 'timeout'. Apr 17 17:22:10 SoftironGGA systemd[1]: Failed to start wicked network management service daemon. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132774 http://bugzilla.opensuse.org/show_bug.cgi?id=1132774#c4 --- Comment #4 from Guillaume GARDET --- Leap 15.1 aarch64 is also affected on openQA: https://openqa.opensuse.org/tests/937951#step/zypper_in/4 Network is broken after a reboot for the exact same reason as seen already on Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132774 http://bugzilla.opensuse.org/show_bug.cgi?id=1132774#c6 --- Comment #6 from Guillaume GARDET --- (In reply to Fabian Vogt from comment #5)

(In reply to Guillaume GARDET from comment #4)

...

Leap 15.1 aarch64 is also affected on openQA: https://openqa.opensuse.org/tests/937951#step/zypper_in/4

Network is broken after a reboot for the exact same reason as seen already on Tumbleweed.

That seems to be a different issue - according to https://openqa.opensuse.org/tests/937951/file/textinfo-info.txt the interface has an IP and /etc/resolv.conf also lists a nameserver. Infra issue?

No, texinfo is run before console_reboot, where the reboot happen. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132774 Andreas Färber changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |afaerber@suse.com OS|Other |openSUSE Factory -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132774 Martin Jambor changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mjambor@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132774 http://bugzilla.opensuse.org/show_bug.cgi?id=1132774#c15 --- Comment #15 from Guillaume GARDET --- Created attachment 807598 --> http://bugzilla.opensuse.org/attachment.cgi?id=807598&action=edit journalctl.log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132774 http://bugzilla.opensuse.org/show_bug.cgi?id=1132774#c17 Michal Koutný changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoutny@suse.com --- Comment #17 from Michal Koutný --- The problems with DBus name discovery are only a consequence of wickedd start (that prusumably provides the interface) failed. In comment 15, we can see the start timed out because of ExecStartPre= (already pointed out above):

Jun 14 11:43:51.036047 SoftironGGA systemd[1]: Starting wicked network management service daemon... Jun 14 11:44:42.406809 SoftironGGA systemd-udevd[474]: e0010000.kcs: Worker [494] processing SEQNUM=2154 is taking a long time Jun 14 11:45:21.156747 SoftironGGA systemd[1]: wickedd.service: Start-pre operation timed out. Terminating. Jun 14 11:45:21.169538 SoftironGGA systemd[1]: wickedd.service: Control process exited, code=killed, status=15/TERM Jun 14 11:45:21.169689 SoftironGGA systemd[1]: wickedd.service: Failed with result 'timeout'.

The directive was added in: version-0.6.54~1^2 6b1f8ed18f25 ("systemd: ask udev to settle before wickedd runs") However, the commit message does not explain why. If the intention was to wait for all devices are discovered, then the proper way is to pull in dependency on systemd-udev-settle.service, i.e. Wants=systemd-udev-settle.service # or Requires= After=systemd-udev-settle.service This way the time spent is accounted where it should be (systemd-udev-settle.service) and it is up to wickedd to fail on its own when it's missing some devices. Another problem is why a particular udev worker gets apparently stuck: Jun 14 11:44:42.406809 SoftironGGA systemd-udevd[474]: e0010000.kcs: Worker [494] processing SEQNUM=2154 is taking a long time (as per comment 3, it's not a device necessary for networking though). -- You are receiving this mail because: You are on the CC list for the bug.