http://bugzilla.opensuse.org/show_bug.cgi?id=1090188 Bug ID: 1090188 Summary: loose or missing ethernet cable delays appearance of shell prompt at boot extra 25 seconds with fixed IP "managed" by Wicked Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: PC OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: mrmazda@earthlink.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 767689 --> http://bugzilla.opensuse.org/attachment.cgi?id=767689&action=edit y2logs from host gb250 To reproduce: 1-NET install 15.0b with complete fixed IP configuration per https://en.opensuse.org/SDB:Linuxrc, and without quiet or splash=silent, on installation kernel cmdline, and without installing Plymouth, to system with total of one ethernet NIC and no wireless hardware 2-disconnect ethernet cable 3-boot without quiet or splash=silent on kernel cmdline, without Plymouth installed, to multi-user.target Actual behavior: 1-wicked takes 30+ seconds to start (according to systemd-analyze blame): Apr 19 02:18:18 gb250 systemd[1]: Starting wicked DHCPv4 supplicant service... Apr 19 02:18:18 gb250 systemd[1]: Starting wicked DHCPv6 supplicant service... Apr 19 02:18:18 gb250 systemd[1]: Starting wicked AutoIPv4 supplicant service... Apr 19 02:18:18 gb250 systemd[1]: Started wicked DHCPv4 supplicant service. Apr 19 02:18:18 gb250 systemd[1]: Started wicked AutoIPv4 supplicant service. Apr 19 02:18:18 gb250 systemd[1]: Started wicked DHCPv6 supplicant service. Apr 19 02:18:18 gb250 systemd[1]: Starting wicked network management service daemon... Apr 19 02:18:19 gb250 systemd[1]: Started wicked network management service daemon. Apr 19 02:18:19 gb250 systemd[1]: Starting wicked network nanny service... Apr 19 02:18:19 gb250 systemd[1]: Started wicked network nanny service. Apr 19 02:18:19 gb250 systemd[1]: Starting wicked managed network interfaces... Apr 19 02:18:49 gb250 wicked[660]: lo up Apr 19 02:18:49 gb250 wicked[660]: eth0 setup-in-progress Apr 19 02:18:49 gb250 systemd[1]: Started wicked managed network interfaces. 2-vtty1 displays "<hostname> systemd[1]: Starting wicked managed network interfaces..." ~30 seconds before any more messages appear on vtty1 3-shell prompt appears on vtty1 ~25 seconds late Expected behavior: 1-boot delay from disconnected ethernet cable is immaterial (just like in 13.1 and earlier using ifup) 2-wicked takes 5-6 seconds to start (according to systemd-analyze blame), without causing any messaging pause on vtty1 3-shell prompt appears promptly :-) Comments: 1-I've been experiencing the boot messaging 25+ second delay (pause), and wait for shell prompt on vtty1 on some installations but not others going all the way back to 13.2. TW on same gb250 host also does this, but 42.3 does not. 42.3 and 42.2 do not on host big31, where TW(sda23), TW(sda12) and 13.2 do. 2-TW on gb250 and TW(sda12) on big31 announce no systemd limit for wicked, delay on vtty1 more than 30 seconds but less than 90 seconds, and systemd-analyze blame on them fails until several minutes have passed with "Bootup is not finished. Please try again later." -- You are receiving this mail because: You are on the CC list for the bug.