Bug ID 910927
Summary wicked/Network is not starting after upgrade
Classification openSUSE
Product openSUSE Distribution
Version 13.2
Hardware x86-64
OS openSUSE 13.2
Status NEW
Severity Critical
Priority P5 - None
Component Network
Assignee bnc-team-screening@forge.provo.novell.com
Reporter s91066@yahoo.gr
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

After the upgrade of my openSUSE 13.1 to openSUSE 13.2 the wicked cannot start
the neteork.
Since I have NFS mount points, sometime the box is not started at all (goes
into Maintenance mode). 

My box uses a static IP (192.168.0.3) and the relevant file seems OK:

----------------------------------------------------------------
cat /etc/sysconfig/network/ifcfg-enp2s0 
BOOTPROTO='static'
IPADDR='192.168.0.3/24'
BROADCAST=''
STARTMODE='auto'
NAME='RTL8111/8168B PCI Express Gigabit Ethernet controller'
ETHTOOL_OPTIONS=''
MTU=''
NETWORK=''
REMOTE_IPADDR=''
-----------------------------------------------------------------

However, after reboot I have no network. I do not use NetworkManager (it's not
even installed), so the only network service installed is the wickedd:

---------------------------------------------------
systemctl list-units -t service | grep -i net
wicked.service         loaded failed failed  wicked managed network interfaces
wickedd-nanny.service  loaded active running wicked network nanny service
wickedd.service        loaded active running wicked network management service
daemon
-----------------------------

I tried to manually start the interface and and I saw the following errors:

ifup enp2s0
wicked: /org/opensuse/Network/Interface.getManagedObjects failed. Server
responds:
wicked: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.opensuse.Network was not provided by any .service files
wicked: Couldn't refresh list of active network interfaces

Restaring again sometimes enables the interface, sometimes it makes no
difference. But always, I can use ifup to start the interface:

ifup enp2s0
enp2s0          up

Trying to find out what the problem is:
ournalctl -p err
Dec 20 18:12:31 peter systemd[1]: Job wickedd-dhcp4.service/start deleted to
break ordering cycle starting with wicked.service/start
Dec 20 18:12:31 peter systemd[1]: Job wickedd-auto4.service/start deleted to
break ordering cycle starting with wicked.service/start
Dec 20 18:12:31 peter systemd[1]: Job wickedd-dhcp6.service/start deleted to
break ordering cycle starting with wicked.service/start
Dec 20 18:12:31 peter systemd[1]: Job auditd.service/start deleted to break
ordering cycle starting with basic.target/start
Dec 20 18:12:31 peter systemd[1]: Job systemd-tmpfiles-setup.service/start
deleted to break ordering cycle starting with basic.target/star
Dec 20 18:12:31 peter systemd[1]: Job YaST2-Second-Stage.service/start deleted
to break ordering cycle starting with wicked.service/start
Dec 20 18:12:31 peter systemd[1]: Job YaST2-Firstboot.service/start deleted to
break ordering cycle starting with wicked.service/start
Dec 20 18:12:31 peter systemd[1]: Job local-fs.target/start deleted to break
ordering cycle starting with basic.target/start
Dec 20 18:12:31 peter systemd[1]: Job wickedd-nanny.service/start deleted to
break ordering cycle starting with wicked.service/start
Dec 20 18:12:31 peter systemd[1]: Job wickedd.service/start deleted to break
ordering cycle starting with wicked.service/start
Dec 20 18:12:32 peter systemd[1]: Job wickedd-nanny.service/start deleted to
break ordering cycle starting with wicked.service/start
Dec 20 18:12:32 peter systemd[1]: Job wickedd.service/start deleted to break
ordering cycle starting with wicked.service/start
Dec 20 18:12:32 peter systemd[1]: Job systemd-tmpfiles-setup.service/start
deleted to break ordering cycle starting with basic.target/star
Dec 20 18:12:32 peter systemd[1]: Job local-fs.target/start deleted to break
ordering cycle starting with basic.target/start


You are receiving this mail because: