Comment # 7 on bug 1005478 from Paul Stynen

Yes I know that enabling DHCP will make 'routes' empty. That is indeed not the
issue.
I am on the same versions of 'wicked' and 'yast2-network' as you are.

Tried to create my 'routes' manually after I switched to static IP via yast.
But that also doesn't work. As you can see below 'wicked' throws away my route.
Any idea ?

linux-64l2:/etc/sysconfig/network # cat routes
default 192.168.131.100 - eth0

linux-64l2:/etc/sysconfig/network # wicked ifstatus eth0
wicked: discarding route not matching any interface: ipv4 0.0.0.0/0 via
192.168.131.100 dev eth0 type unicast table main scope universe protocol boot
eth0            device-not-running
      link:     #2, state up, mtu 1500
      type:     ethernet, hwaddr d0:27:88:52:a2:5c
      config:   compat:suse:/etc/sysconfig/network/ifcfg-eth0
      leases:   ipv4 static failed
      addr:     ipv4 192.168.131.103/32 [static]