What | Removed | Added |
---|---|---|
Status | CONFIRMED | IN_PROGRESS |
Flags | needinfo?(ro@suse.com) |
I have reproduced this issue with wicked 0.6.19. The root cause is the starting (out-of-)order of policies at nanny. For setups like br0{eth0}, vlan1@eth0 when vlan1 and eth0 policies are applied first, eth0 worker attempts to start linkUp without waiting for bridge and enslavement. This issue has been resolved with https://github.com/openSUSE/wicked/pull/574 pull request, which is a part of released wicked 0.6.20. The issue is not reproducible with wicked 0.6.20. Could you please confirm?