Bug 1145159

Summary: Problems with wicked daemon
Product: [openSUSE] openSUSE Tumbleweed Reporter: Heinz Hill <hill.heinz>
Component: BasesystemAssignee: wicked maintainers <wicked-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: alynx.zhou, rtorreromarijnissen
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Heinz Hill 2019-08-10 07:09:36 UTC 
After the updates of 7.8.2019 the wicked service starts, but then stops:
* wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
   Active: active (exited) since Sat 2019-08-10 08:49:28 CEST; 13min ago
  Process: 1378 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS)
  Process: 2789 ExecReload=/usr/sbin/wicked --systemd ifreload all (code=exited, status=0/SUCCESS)
 Main PID: 1378 (code=exited, status=0/SUCCESS)
Aug 10 08:48:58 linux-czsx systemd[1]: Starting wicked managed network interfaces...
Aug 10 08:49:28 linux-czsx wicked[1378]: lo              setup-in-progress
Aug 10 08:49:28 linux-czsx wicked[1378]: wlp0s20u8       device-not-running
Aug 10 08:49:28 linux-czsx systemd[1]: Started wicked managed network interfaces.
Aug 10 08:50:29 linux-czsx systemd[1]: Reloading wicked managed network interfaces.
Aug 10 08:50:53 linux-czsx wicked[2789]: wlp0s20u8       device-ready
Aug 10 08:50:53 linux-czsx wicked[2789]: wlp0s20u8       up
Aug 10 08:50:53 linux-czsx systemd[1]: Reloaded wicked managed network interfaces.

I have to restart the service manually via yast->network settings (is there another way of starting the daemon?).
Before the update everything worked fine.

How can I fix this problem, so I don't have to start the service manually?
Thanks for your help
Comment 1 Rubén Torrero Marijnissen 2020-03-25 15:57:14 UTC 
Hi,

This issue is a duplicate of https://bugzilla.suse.com/show_bug.cgi?id=1144670 caused probably due to wrong ordering of the wpa_supplicant unit

*** This bug has been marked as a duplicate of bug 1144670 ***