Hard to tell what is causing the problem here without detailed logs.

Could you first set this:
# sed -i s/use-nanny\>false/use-nanny\>true/g /etc/wicked/common.xml
# systemctl restart wickedd

and try whether it helps after the reboot? If this is timeout of some sort, this could help.

Otherwise if the issue is still appearing could you please provide logs as described here:

https://en.opensuse.org/openSUSE:Bugreport_wicked

Thanks for reporting.

Changing the use-nanny setting did not affect the behaviour, except that previously "rcnetwork restart" would bring up the wireless interface.  Now only "rcwicked restart" will do so.

I'll attach logs in a moment.

Created attachment 625887 [details]
logs as requested

This bug seems to be affecting 13.2 as well. A simple ifdown / ifup fixes the problem until the next reboot.
# ifstatus wlp2s0 
wlp2s0          up
      link:     #3, state up, mtu 1500
      type:     wireless
      config:   compat:/etc/sysconfig/network/ifcfg-wlp2s0
      addr:     ipv6 2601:1:3380:7ba2:8286:f2ff:fe09:5871/64
      addr:     ipv6 2601:1:3380:7ba2:e42e:6949:9170:e937/64
# ifdown wlp2s0 ; ifup wlp2s0 
wlp2s0          device-ready
wlp2s0          up
# ifstatus wlp2s0 
wlp2s0          up
      link:     #3, state up, mtu 1500
      type:     wireless
      config:   compat:/etc/sysconfig/network/ifcfg-wlp2s0
      leases:   ipv4 dhcp granted
      leases:   ipv6 dhcp granted
      addr:     ipv4 192.168.76.25/24 [dhcp]
      addr:     ipv6 2601:1:3380:7ba2:8286:f2ff:fe09:5871/64
      addr:     ipv6 2601:1:3380:7ba2:e42e:6949:9170:e937/64
      route:    ipv4 default via 192.168.76.1
      route:    ipv6 default via fe80::62a4:4cff:fe27:a700

There is a patch to address this issue at:
https://github.com/openSUSE/wicked/pull/523

Also there is my private, temporary RPM repo (which I can remove at any time, without any warning ;-) ) where this patch is applied:
https://build.opensuse.org/package/show/home:pwieczorkiewicz:branches:network:wicked:master/wicked

You can download and install wicked RPMS for you target platform from there and re-test.

Thanks!

The packages mentioned in comment #5 worked for me and resolved the problem.

Pawel, your RPM from Comment 5 also fixed the problem for me on 13.2.

Thanks for re-testing. The patch will be available with wicked 0.6.18 release, which is due soon.

Habe den Fix installiert. Bei einenen Reboot hat es funktioniert, aber
am naechsten Tag, bei einen cold start, das gleiche Problem. Musste
wieder ifup ..... anwenden um ins Internet zu kommen, bzw fruehere Version von wicked. Betroffenes Geraet ist ein Desktop. Ein alter Sony Laptop (32 bit) hat keine Probleme

Created attachment 626433 [details]
logs after activating the interface with ifup

Created attachment 626434 [details]
logs after a reboot with interface not connected

I have the same experience as comment #9
With the rpms kindly provided by Pawel it was not possible to connect to the network.
I attached 2 packages with logs:
1.) after installing the rpms, rebooting and connecting to the network with ifup (626433)
2.) again reboot with the provided rpms, no connection to network (626434)

(In reply to Martin Dornblüth from comment #12)
> I have the same experience as comment #9
> With the rpms kindly provided by Pawel it was not possible to connect to the
> network.
> I attached 2 packages with logs:
> 1.) after installing the rpms, rebooting and connecting to the network with
> ifup (626433)
> 2.) again reboot with the provided rpms, no connection to network (626434)

This is interesting, because both logs you provided show that wireless interface is up and running:

wlp4s1          up
      link:     #3, state up, mtu 1500
      type:     wireless
      control:  none
      config:   compat:/etc/sysconfig/network/ifcfg-wlp4s1,
                uuid: a5893ad4-abc2-5d87-9617-a28eaf9e3235
      leases:   ipv4 dhcp granted [group]
      leases:   ipv6 dhcp granted [group]
      addr:     ipv6 2002:25d1:3486:0:792a:be2a:4865:3089/64
                dynamic|temporary lifetime 6927/3327
      addr:     ipv6 2002:25d1:3486:0:b248:7aff:febf:7199/64
                dynamic lifetime 6927/3327
      addr:     ipv6 fe80::b248:7aff:febf:7199/64
      addr:     ipv4 192.168.178.20/24 [dhcp]
      route:    ipv4 0.0.0.0/0 via 192.168.178.1 dev #0 type unicast table main scope universe protocol dhcp
      route:    ipv4 192.168.178.0/24 dev #0 type unicast table main scope link protocol kernel pref-src 192.168.178.20
      route:    ipv6 2002:25d1:3486::/64 dev #0 type unicast table main scope universe protocol kernel priority 256
      route:    ipv6 fe80::/64 dev #0 type unicast table main scope universe protocol kernel priority 256
      route:    ipv6 ::/0 via fe80::2665:11ff:fe05:3fbe dev #0 type unicast table main scope universe protocol ra priority 1024


and the second one:
wlp4s1          up
      link:     #3, state up, mtu 1500
      type:     wireless
      control:  none
      config:   compat:/etc/sysconfig/network/ifcfg-wlp4s1,
                uuid: a5893ad4-abc2-5d87-9617-a28eaf9e3235
      leases:   ipv4 dhcp granted [group]
      leases:   ipv6 dhcp requesting [group]
      addr:     ipv4 192.168.178.20/24 [dhcp]
      addr:     ipv6 fe80::b248:7aff:febf:7199/64
      route:    ipv4 0.0.0.0/0 via 192.168.178.1 dev #0 type unicast table main scope universe protocol dhcp
      route:    ipv4 192.168.178.0/24 dev #0 type unicast table main scope link protocol kernel pref-src 192.168.178.20
      route:    ipv6 fe80::/64 dev #0 type unicast table main scope universe protocol kernel priority 256

what you probably mean is:
eno1            setup-in-progress
      link:     #2, state device-up, mtu 1500
      type:     ethernet, hwaddr 78:24:af:8e:b2:81
      control:  none
      config:   compat:/etc/sysconfig/network/ifcfg-eno1,
                uuid: c9021235-fdfa-5527-b247-c91c0b701e8f

But here apparently there is no cable plugged in, thus no link and interface is left in setup-in-progress state.
Could you please provide more info what is the problem here?

For me this:
After starting no network.
- Network Service is started, connected Wi-Fi,
- But the interface does not get the static IP
By restarting the network service the static IP is assigned and the network is functioning.

Information:
Laptop oS 13.2 and WLAN-Network.

Installiert:

zy_se -i | grep wicked
i | libwicked-0-6 | package | 0.6.17-12.1 |x86_64 |
openSUSE-13.2-Update
i | wicked | package | 0.6.17-12.1 |x86_64 |
openSUSE-13.2-Update
i | wicked-service | package | 0.6.17-12.1 |x86_64 |
openSUSE-13.2-Update

wicked-Services:

linux:~ # systemctl | grep wicked
wicked.service loaded active exited
wickedd-auto4.service loaded active running
wickedd-dhcp4.service loaded active running
wickedd-dhcp6.service loaded active running
wickedd-nanny.service loaded active running
wickedd.service loaded active running

Inhalt u.a. in ifcfg-wls1:

BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IFPLUGD_PRIORITY='nil'
IPADDR='192.168.0.6/24'
MTU=''
NAME='AR9285 Wireless Network Adapter (PCI-Express)'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'

systemctl _before_  Restart Network:

linux:~ # systemctl status network.service
wicked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
Active: active (exited) since Tue 2015-03-03 19:44:35 CET; 2min 13s ago
Process: 798 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited,
status=0/SUCCESS)
Main PID: 798 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/wicked.service

Mar 03 19:44:35 linux wicked[798]: lo up
Mar 03 19:44:35 linux wicked[798]: wls1 up
linux:~ #
linux:~ #
linux:~ # ifconfig
wls1 Link encap:Ethernet HWaddr 74:F0:6D:74:5E:3E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:121 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:40682 (39.7 Kb) TX bytes:288 (288.0 b)

systemctl _after_ Restart:

linux:~ # systemctl status network.service
wicked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
Active: active (exited) since Tue 2015-03-03 20:02:25 CET; 35s ago
Process: 3187 ExecStop=/usr/sbin/wicked --systemd ifdown all (code=exited,
status=0/SUCCESS)
Process: 3194 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited,
status=0/SUCCESS)
Main PID: 3194 (code=exited, status=0/SUCCESS)

Mar 03 20:02:25 linux wicked[3194]: lo up
Mar 03 20:02:25 linux wicked[3194]: wls1 up

linux:~ # ifconfig
wls1 Link encap:Ethernet HWaddr 74:F0:6D:74:5E:3E
inet addr:192.168.0.6 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:804 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:267903 (261.6 Kb) TX bytes:4992 (4.8 Kb)

Hi Pawel,

your fix works for me on my machine. Thank you.

My problem is solved with the new RPM. Thanks Pawel.

OK the fix is also working for me. Since is used a 1-click install from Pawels website, I didn't notice that an ealier version of wicked was installed.
After checking everything again, I installed the right version and everything is working beautifully.

Hello Pawel,
I have a desktop PC with eth on board, butnot used. wlp4s1 is the only interface, which connectets to network (wireless)
I attach logfiles and a description of the actions I taken.

Kind regards
Martin

Created attachment 626883 [details]
logs from the Update

Created attachment 626884 [details]
Description of the steps done during the update

(In reply to Martin Dornblüth from comment #18)
> Hello Pawel,
> I have a desktop PC with eth on board, butnot used. wlp4s1 is the only
> interface, which connectets to network (wireless)
> I attach logfiles and a description of the actions I taken.
> 
> Kind regards
> Martin

Hi Martin,

I believe the problem here is that the right RPMs were not installed. Thus after reboot you see the same issue. In order to install them (here I am assuming you are using 13.2) do the following steps:

Variant 1:
- wget http://download.opensuse.org/repositories/home:/pwieczorkiewicz:/branches:/network:/wicked:/master/openSUSE_13.2/x86_64/libwicked-0-6-0.6.17-10.1.x86_64.rpm
- wget http://download.opensuse.org/repositories/home:/pwieczorkiewicz:/branches:/network:/wicked:/master/openSUSE_13.2/x86_64/wicked-0.6.17-10.1.x86_64.rpm
- wget http://download.opensuse.org/repositories/home:/pwieczorkiewicz:/branches:/network:/wicked:/master/openSUSE_13.2/x86_64/wicked-service-0.6.17-10.1.x86_64.rpm
- sudo rpm -Uhv --force --nodeps libwicked-0-6-0.6.17-10.1.x86_64.rpm wicked-0.6.17-10.1.x86_64.rpm wicked-service-0.6.17-10.1.x86_64.rpm
- systemctl restart wickedd

Variant 2:
- wait for official wicked 0.6.18 release :-)

BTW: In case of variant 1 do not forget to get back to the official 13.2:Update track, when 0.6.18 wicked is out (you will be informed by comments on this bug), by issuing zypper dup.

 Hi Pavel,
 did not send my problem or log in time. 
 But I'm paticipating from your solution cause your patch solved my problem too :-)
 So I'd like to say: Thanks for your job !
 Regards
 Sven

(In reply to Pawel Wieczorkiewicz from comment #21)
> (In reply to Martin Dornblüth from comment #18)
> > Hello Pawel,
> > I have a desktop PC with eth on board, butnot used. wlp4s1 is the only
> > interface, which connectets to network (wireless)
> > I attach logfiles and a description of the actions I taken.
> > 
> > Kind regards
> > Martin
> 
> Hi Martin,
> 
> I believe the problem here is that the right RPMs were not installed. Thus
> after reboot you see the same issue. In order to install them (here I am
> assuming you are using 13.2) do the following steps:
> 
> Variant 1:
> - wget
> http://download.opensuse.org/repositories/home:/pwieczorkiewicz:/branches:/
> network:/wicked:/master/openSUSE_13.2/x86_64/libwicked-0-6-0.6.17-10.1.
> x86_64.rpm
> - wget
> http://download.opensuse.org/repositories/home:/pwieczorkiewicz:/branches:/
> network:/wicked:/master/openSUSE_13.2/x86_64/wicked-0.6.17-10.1.x86_64.rpm
> - wget
> http://download.opensuse.org/repositories/home:/pwieczorkiewicz:/branches:/
> network:/wicked:/master/openSUSE_13.2/x86_64/wicked-service-0.6.17-10.1.
> x86_64.rpm
> - sudo rpm -Uhv --force --nodeps libwicked-0-6-0.6.17-10.1.x86_64.rpm
> wicked-0.6.17-10.1.x86_64.rpm wicked-service-0.6.17-10.1.x86_64.rpm
> - systemctl restart wickedd
> 
> Variant 2:
> - wait for official wicked 0.6.18 release :-)
> 
> BTW: In case of variant 1 do not forget to get back to the official
> 13.2:Update track, when 0.6.18 wicked is out (you will be informed by
> comments on this bug), by issuing zypper dup.

Hello Pawel,
thanks for your patience and support! I tried Variant 1 and finaly I made it ;-)
With your how to I was able to apply the rpms and the problem is fixed.

Kind regards
Martin

Patch has been submitted to the master git repo. It should be soon available at OBS repo network:wicked:master.

This is an autogenerated message for OBS integration:
This bug (921218) was mentioned in
https://build.opensuse.org/request/show/303888 Factory / wicked
https://build.opensuse.org/request/show/303889 13.2 / wicked

openSUSE-RU-2015:0820-1: An update that has 8 recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 907215,907694,918662,920070,920889,921218,927065,927616
CVE References: 
Sources used:
openSUSE 13.2 (src):    wicked-0.6.18-15.1

SUSE-RU-2015:0924-1: An update that has 14 recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 904323,905421,907215,907694,909307,911299,911562,914792,918662,920070,920889,921218,927065,927616
CVE References: 
Sources used:
SUSE Linux Enterprise Server 12 (src):    wicked-0.6.18-16.1
SUSE Linux Enterprise Desktop 12 (src):    wicked-0.6.18-16.1