Comment # 2 on bug 1206674 from simon becherer

Same here,

is reproduceable if you have a "bond" configuration
(normal hardware configuration will work)

(according to andrei at mailinglist  users@lists.opensuse.org)

long (about one year) not updated tumbleweed was
running fine.
then update to tumbleweed 20221228 and network is not working.
now at 20230102 still same.

here what i have, and a workaround later in this comment:

if it is working, it looks like this:

================================================
wicked ifstatus all

lo              up
      link:     #1, state up
      type:     loopback
      config:   compat:suse:/etc/sysconfig/network/ifcfg-lo
      leases:   ipv4 static granted
      leases:   ipv6 static granted
      addr:     ipv4 127.0.0.1/8 [static]
      addr:     ipv6 ::1/128 [static]

enp3s0          enslaved
      link:     #2, state up, mtu 1500, master bond0
      type:     ethernet, hwaddr 18:67:b0:b9:a6:58
      config:   compat:suse:/etc/sysconfig/network/ifcfg-enp3s0

wlp2s0          up
      link:     #3, state up, mtu 1500
      type:     wireless, state established, ssid XAuaLiwaru9835,
WPA2-PSK+WPA-PSK
      config:   compat:suse:/etc/sysconfig/network/ifcfg-wlp2s0

bond0           up
      link:     #4, state up, mtu 1500
      type:     bond, mode active-backup, hwaddr 18:67:b0:b9:a6:58
      config:   compat:suse:/etc/sysconfig/network/ifcfg-bond0
      leases:   ipv4 static granted
      addr:     ipv4 192.168.0.23/24 [static]
      route:    ipv4 default via 192.168.0.99 [static]

====================================
it is configured that if cable (enp3s0) is plugged in,
it will use cable, and if not plugged in it will switch to
whireless (wlp2s0)
====================================
if its not working (before starting manually) it has
the status: "device-not-running" for enp3s0 wlp2s0 and bond0
====================================

after playing around i found out that the command:
ip link set enp3s0 up
ip link set wlp2s0 up

will bring the network cards UP,
but this i have to enter manually,

AND
wicked ifup enp3s0
wicked ifup wlp2s0

will NOT bring the network cards UP.
(therefore wicked will during boot hang and run out of
time, then boot continues

==========================================
here from boot:
Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked AutoIPv4 supplicant
service...
Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked DHCPv4 supplicant
service...
Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked DHCPv6 supplicant
service...
Dez 29 21:54:08 becherer7 systemd[1]: Started wicked DHCPv6 supplicant service.
Dez 29 21:54:08 becherer7 systemd[1]: Started wicked DHCPv4 supplicant service.
Dez 29 21:54:08 becherer7 systemd[1]: Started wicked AutoIPv4 supplicant
service.
Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked network management
service daemon...
Dez 29 21:54:08 becherer7 systemd[1]: Started wicked network management service
daemon.
Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked network nanny service...
Dez 29 21:54:08 becherer7 systemd[1]: Started wicked network nanny service.
Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked managed network
interfaces...
Dez 29 21:54:38 becherer7 wicked[1227]: lo              up
Dez 29 21:54:38 becherer7 wicked[1227]: enp3s0          device-not-running
Dez 29 21:54:38 becherer7 wicked[1227]: wlp2s0          device-not-running
Dez 29 21:54:38 becherer7 wicked[1227]: bond0           device-not-running
Dez 29 21:54:38 becherer7 systemd[1]: Finished wicked managed network
interfaces.

=================================================
and here when i try manually using wicked:
Dez 29 22:19:14 becherer7 wickedd-nanny[1226]: device wlp2s0: call to
org.opensuse.Network.Interface.waitLinkUp() failed: General failure
Dez 29 22:19:14 becherer7 wickedd-nanny[1226]: wlp2s0: failed to bring up
device, still continuing
Dez 29 22:19:19 becherer7 wickedd-nanny[1226]: device enp3s0: call to
org.opensuse.Network.Interface.waitLinkUp() failed: General failure
Dez 29 22:19:19 becherer7 wickedd-nanny[1226]: enp3s0: failed to bring up
device, still continuing
===================================================

workaround for boot:
as allesandro sturniolo wrote, use
ip link set enp3s0 up
ip link set wlp2s0 up 
(in my setup)

so make a file 
netz-wicked-workaround.service

--------file ----------------------------
[Unit]
Description=netz-wicked-workaround
After=wicked.service

[Service]
Type=simple
ExecStart=/usr/bin/netz
RemainAfterExit=no

[Install]
WantedBy=multi-user.target
-------endfile --------------------------------

copy this to
/etc/systemd/system
--------------------------------------
make a file netz

-------------- file (for my setup)-------------
#!/bin/bash

sudo ip link set wlp2s0 up
sudo ip link set enp3s0 up
----------- endfile--------------------
copy it to /usr/bin/netz
and give them executable rights
----------------------------------------
use yast2 to start the new service at boot
netz-wicked-workaround.service
-------------------------------------


simoN