Comment # 4 on bug 917106 from Pawel Wieczorkiewicz

(In reply to Andrew Findlay from comment #3)
> Created attachment 622873 [details]
> Reboot log with wicked nanny enabled
> 
> I now have a workaround for this.
> I enabled nanny by adding this to /etc/wicked/local.xml:
> 
> <!-- Local configuration file -->
> <config>
>   <use-nanny>true</use-nanny>
> </config>
> 
> Now the WiFi interface comes up at boot-time as it should.
> Logfile attached (with passphrases removed).
> The startup process looks rather different now.

Excellent! This was basically the next step I wanted to test here.
>From wicked point of view there is nothing wrong here: initially, during
boot-up ifup all, we read rfkill OFF event from /dev/rfkill which later gets
set to ON.

Nanny works with this scenario as this is hotplug scenario and it is dedicated
to deal with situation like this one.

The remaining question could be why rfkill is updated that far with your
kernel/machine. But it does not seem like wicked related issue.

*** This bug has been marked as a duplicate of bug 915025 ***