Comment # 24 on bug 1229745 from David Rankin

I can confirm this issue with a dup last night for Tumbleweed where WiFi is no
longer started by wicked at boot. This install had been flawless for months
until the dup last night. On reboot, the network fails to be started.

Journal entries:

Aug 27 03:31:40 wizard systemd[1]: Reached target Socket Units.
Aug 27 03:31:40 wizard systemd[1]: D-Bus System Message Bus is inactive.
Aug 27 03:31:40 wizard systemd[1]: Dependency failed for wicked network
management service daemon.
Aug 27 03:31:40 wizard systemd[1]: wickedd.service: Job wickedd.service/start
failed with result 'dependency'.
Aug 27 03:31:40 wizard systemd[1]: Dependency failed for wicked DHCPv6
supplicant service.
Aug 27 03:31:40 wizard systemd[1]: wickedd-dhcp6.service: Job
wickedd-dhcp6.service/start failed with result 'dependency'.
Aug 27 03:31:40 wizard systemd[1]: Dependency failed for wicked network nanny
service.
Aug 27 03:31:40 wizard systemd[1]: wickedd-nanny.service: Job
wickedd-nanny.service/start failed with result 'dependency'.
Aug 27 03:31:40 wizard systemd[1]: Dependency failed for wicked DHCPv4
supplicant service.
Aug 27 03:31:40 wizard systemd[1]: wickedd-dhcp4.service: Job
wickedd-dhcp4.service/start failed with result 'dependency'.
Aug 27 03:31:40 wizard systemd[1]: Dependency failed for wicked AutoIPv4
supplicant service.
Aug 27 03:31:40 wizard systemd[1]: wickedd-auto4.service: Job
wickedd-auto4.service/start failed with result 'dependency'.
Aug 27 03:31:40 wizard systemd[1]: Reached target Basic System.

Something broke D-Bus ordering so now wickedd fails to start the network.