|
Bugzilla – Full Text Bug Listing |
| Summary: | factory: wicked fails to bring up vlan device with "no-device" message | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Ruediger Oertel <ro> |
| Component: | Network | Assignee: | wicked maintainers <wicked-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | chcao, ebischoff, kdupke, pwieczorkiewicz, ro |
| Version: | Current | Flags: | pwieczorkiewicz:
needinfo?
(ro) |
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Ruediger Oertel
2015-07-27 16:20:33 UTC
feel free to play with it, it's still happening: Fatou:~ # rcnetwork status * wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled) Active: active (exited) since Fri 2015-07-31 11:28:09 CEST; 7h ago Process: 1253 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 1253 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service Jul 31 11:27:39 Fatou systemd[1]: Starting wicked managed network interfaces... Jul 31 11:28:09 Fatou wicked[1253]: lo up Jul 31 11:28:09 Fatou wicked[1253]: enp0s25 enslaved Jul 31 11:28:09 Fatou wicked[1253]: vlan1 up Jul 31 11:28:09 Fatou wicked[1253]: br0 up Jul 31 11:28:09 Fatou wicked[1253]: vlan15 no-device Jul 31 11:28:09 Fatou systemd[1]: Started wicked managed network interfaces. Fatou:~ # ifdown vlan15 Fatou:~ # rcnetwork status * wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled) Active: active (exited) since Fri 2015-07-31 11:28:09 CEST; 7h ago Process: 1253 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 1253 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service Jul 31 11:27:39 Fatou systemd[1]: Starting wicked managed network interfaces... Jul 31 11:28:09 Fatou wicked[1253]: lo up Jul 31 11:28:09 Fatou wicked[1253]: enp0s25 enslaved Jul 31 11:28:09 Fatou wicked[1253]: vlan1 up Jul 31 11:28:09 Fatou wicked[1253]: br0 up Jul 31 11:28:09 Fatou wicked[1253]: vlan15 no-device Jul 31 11:28:09 Fatou systemd[1]: Started wicked managed network interfaces. Fatou:~ # ifup vlan15 vlan15 up Fatou:~ # rcnetwork status * wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled) Active: active (exited) since Fri 2015-07-31 11:28:09 CEST; 7h ago Process: 1253 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 1253 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service Jul 31 11:27:39 Fatou systemd[1]: Starting wicked managed network interfaces... Jul 31 11:28:09 Fatou wicked[1253]: lo up Jul 31 11:28:09 Fatou wicked[1253]: enp0s25 enslaved Jul 31 11:28:09 Fatou wicked[1253]: vlan1 up Jul 31 11:28:09 Fatou wicked[1253]: br0 up Jul 31 11:28:09 Fatou wicked[1253]: vlan15 no-device Jul 31 11:28:09 Fatou systemd[1]: Started wicked managed network interfaces. Fatou:~ # 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?
(In reply to Pawel Wieczorkiewicz from comment #3) > 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. > BTW: 0.6.20 has fixes for most urgent problems related to this issue. Next release 0.6.21 will contain more fixes and improvements in this area. 0.6.20 fixes the issue for me on fatou. *** Bug 942460 has been marked as a duplicate of this bug. *** |