kernel 4.0.1.1 : wicked and DHCP fails at boot

Hello,

I have installed the last kernel (4.0.1-1) from tumbleweed today.
I use normally the xen kernel and I have a bridge br0 defined in network interface
Hardware is a HP proliant ML350

After reboot I receive an error that the dhcp server cannot be started

systemctl status dhcpd
● dhcpd.service - ISC DHCPv4 Server
   Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2015-05-06 21:48:56 CEST; 1min 22s ago
  Process: 1236 ExecStart=/usr/lib/dhcp/dhcpd -4 start (code=exited, status=1/FAILURE)

May 06 21:48:56 hpprol2 dhcpd[1627]: requesting help.
May 06 21:48:56 hpprol2 dhcpd[1627]:
May 06 21:48:56 hpprol2 dhcpd[1627]: If you did get this software from ftp.isc.org and have not
May 06 21:48:56 hpprol2 dhcpd[1627]: yet read the README, please read it before requesting help.
May 06 21:48:56 hpprol2 dhcpd[1236]: Starting ISC DHCPv4 Server
May 06 21:48:56 hpprol2 dhcpd[1236]: please see /var/log/rc.dhcpd.log for details ..failed
May 06 21:48:56 hpprol2 systemd[1]: dhcpd.service: control process exited, code=exited status=1
May 06 21:48:56 hpprol2 systemd[1]: Failed to start ISC DHCPv4 Server.
May 06 21:48:56 hpprol2 systemd[1]: Unit dhcpd.service entered failed state.
May 06 21:48:56 hpprol2 systemd[1]: dhcpd.service failed.

in var/log/rc.dhcpd.log i have

No subnet declaration for br0 (no IPv4 addresses).
** Ignoring requests on br0.  If this is not what
   you want, please write a subnet declaration
   in your dhcpd.conf file for the network segment
   to which interface br0 is attached. **

the wicked service is also down and I think that this is the reason why the dhcp server doesn’t start

systemctl status wicked
● wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
   Active: inactive (dead)

May 06 22:25:35 hpprol2 systemd[1]: Job wicked.service/start deleted to break ordering cycle starting with network.target/start
May 06 22:25:39 hpprol2 systemd[1]: Job wicked.service/start deleted to break ordering cycle starting with network.target/start
May 06 22:25:40 hpprol2 systemd[1]: Job wicked.service/start deleted to break ordering cycle starting with network.target/start

Definition of br0 in Yast network interface:

  • must be started at boot
  • has a fixed IP address (192.168.1.120)
  • is a bridge linked with port enol which is a Broadcom ethernet controller

This error didn’t occurs withe kernel 3.xx

Solving:
if I go in the network parameter reviewing all the tabs (no changes) and saving the definition then the wicked service starts and dhcp server can also be started

systemctl status wicked
● wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)  
   Active: active (exited) since Wed 2015-05-06 21:53:29 CEST; 18min ago 
 Main PID: 8595 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/wicked.service 
May 06 21:53:24 hpprol2 systemd[1]: Starting wicked managed network interfaces... 
May 06 21:53:29 hpprol2 wicked[8595]: lo              up 
May 06 21:53:29 hpprol2 wicked[8595]: br0             up 
May 06 21:53:29 hpprol2 wicked[8595]: eno1            enslaved 
May 06 21:53:29 hpprol2 systemd[1]: Started wicked managed network interfaces.  
May 06 21:53:36 hpprol2 systemd[1]: Started wicked managed network interfaces.  
May 06 21:54:44 hpprol2 systemd[1]: Started wicked managed network interfaces.  
May 06 21:54:49 hpprol2 systemd[1]: Started wicked managed network interfaces.

systemctl status dhcpd
● dhcpd.service - ISC DHCPv4 Server
   Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2015-05-06 21:54:44 CEST; 16min ago
 Main PID: 10144 (dhcpd)
   CGroup: /system.slice/dhcpd.service
           └─10144 /usr/sbin/dhcpd -4 -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid -chroot /var/lib/dhcp -lf /db/dhcpd.leases -user dhcpd -group nogroup br0

seems that wicked cannot be started correctly during boot with this new kernel. This problem occurs at each reboot
not sure if this is related to the kernel or to wicked: journalctl doesn’t show any error for wicked during boot
This error occurs also with the desktop kernel

any idea?
Regards
Philippe

I am not having that problem. The network came up just fine (using “wicked”) with kernel 4.0.1

Thanks for your feedback,

I changed the fixed IP address of br0 and thereafter reset it to the original address. After reboot (XEN kernel) the network is now started correctly.
I didn’t find any new or updated file in /etc but this solved the problem.
I need still testing with the desktop kernel

Regards
Philippe