Bug 1167886 - Wicked doesn't get the connection during boot
Summary: Wicked doesn't get the connection during boot
Status: RESOLVED DUPLICATE of bug 1166933
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Network (show other bugs)
Version: Leap 15.2
Hardware: Other Other
: P2 - High : Normal (vote)
Target Milestone: ---
Assignee: wicked maintainers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-27 11:29 UTC by Daniel VE
Modified: 2020-04-06 13:14 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
YaST device summary (21.34 KB, image/png)
2020-03-27 11:29 UTC, Daniel VE
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel VE 2020-03-27 11:29:24 UTC
Created attachment 834037 [details]
YaST device summary

With my ath5k wireless card I need to activate the connection with ifup after logged. I don't see any warning in logs.
Comment 1 Daniel VE 2020-03-27 19:11:07 UTC
Services detailed:

* wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
   Active: active (exited) since Fri 2020-03-27 19:12:01 CET; 1min 47s ago
  Process: 1112 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS)
 Main PID: 1112 (code=exited, status=0/SUCCESS)
    Tasks: 0
   CGroup: /system.slice/wicked.service

Mar 27 19:11:35 myhost systemd[1]: Starting wicked managed network interfaces...
Mar 27 19:12:01 myhost wicked[1112]: lo              up
Mar 27 19:12:01 myhost wicked[1112]: wlan0           device-not-running
Mar 27 19:12:01 myhost systemd[1]: Started wicked managed network interfaces.

* wickedd.service - wicked network management service daemon
   Loaded: loaded (/usr/lib/systemd/system/wickedd.service; indirect; vendor preset: disabled)
   Active: active (running) since Fri 2020-03-27 19:11:35 CET; 2min 53s ago
 Main PID: 1101 (wickedd)
    Tasks: 1
   CGroup: /system.slice/wickedd.service
           `-1101 /usr/sbin/wickedd --systemd --foreground

Mar 27 19:11:35 myhost systemd[1]: Starting wicked network management service daemon...
Mar 27 19:11:35 myhost systemd[1]: Started wicked network management service daemon.
Mar 27 19:12:00 myhost wickedd[1101]: ni_wpa_interface_bind(wlan0): Operation not permitted
Mar 27 19:12:00 myhost wickedd[1101]: wpa_supplicant doesn't know interface wlan0

* wickedd-nanny.service - wicked network nanny service
   Loaded: loaded (/usr/lib/systemd/system/wickedd-nanny.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2020-03-27 19:11:35 CET; 3min 15s ago
 Main PID: 1107 (wickedd-nanny)
    Tasks: 1
   CGroup: /system.slice/wickedd-nanny.service
           `-1107 /usr/sbin/wickedd-nanny --systemd --foreground

Mar 27 19:11:35 myhost systemd[1]: Starting wicked network nanny service...
Mar 27 19:11:35 myhost systemd[1]: Started wicked network nanny service.
Mar 27 19:12:00 myhost wickedd-nanny[1107]: device wlan0: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure
Mar 27 19:12:00 myhost wickedd-nanny[1107]: wlan0: failed to bring up device, still continuing
Comment 2 Rubén Torrero Marijnissen 2020-04-06 13:14:10 UTC
Closing as duplicate as this issue has been reported several times.

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