http://bugzilla.suse.com/show_bug.cgi?id=945601
http://bugzilla.suse.com/show_bug.cgi?id=945601#c6
Marius Tomaschewski changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CONFIRMED
CC| |mt@suse.com
--- Comment #6 from Marius Tomaschewski ---
There are the following configs:
2015-09-16T10:31:04.147086+02:00 xrated wicked[1195]:
ni_sysconfig_read(/etc/sysconfig/network/ifcfg-enp0s20u2)
2015-09-16T10:31:04.147172+02:00 xrated wicked[1195]:
ni_sysconfig_read(/etc/sysconfig/network/ifcfg-eth0)
2015-09-16T10:31:04.147270+02:00 xrated wicked[1195]:
ni_sysconfig_read(/etc/sysconfig/network/ifcfg-enp0s20u1)
2015-09-16T10:31:04.147360+02:00 xrated wicked[1195]:
ni_sysconfig_read(/etc/sysconfig/network/ifcfg-lo)
which are added to nanny:
2015-09-16T10:31:04.148803+02:00 xrated wicked[1195]: enp0s20u1: adding policy
policy__enp0s20u1 to nanny
2015-09-16T10:31:04.152173+02:00 xrated wicked[1195]: enp0s20u2: adding policy
policy__enp0s20u2 to nanny
2015-09-16T10:31:04.154749+02:00 xrated wicked[1195]: eth0: adding policy
policy__eth0 to nanny
2015-09-16T10:31:04.157317+02:00 xrated wicked[1195]: lo: adding policy
policy__lo to nanny
nanny finished it's steps on (lo and) eth0:
2015-09-16T10:31:12.033392+02:00 xrated wickedd-nanny[1193]: eth0: successfully
transitioned from addrconf-up to network-up
and there is nothing it could currently do with the another devices,
which aren't available:
2015-09-16T10:31:12.033579+02:00 xrated wickedd-nanny[1193]: waiting for 0
devices to become ready (0 explicitly requested)
but wicked ifup still waits for the missed enp0s20u1 and enp0s20u2
to appear until the end of ifup --timeout:
2015-09-16T10:31:34.151449+02:00 xrated wicked[1195]: Interface wait time
reached
Whether to wait or not depends on the configuration:
BOOTPROTO=auto/[on]boot/nfsroot => always wait
vs.
BOOTPROTO=hotplug & co => wait only if device exists
This is not catched properly in ifup.
Bug description "wicked always take > 30sec for usual dhcp setup" is simply
wrong -- regardless of the above behavior :-)
--
You are receiving this mail because:
You are on the CC list for the bug.
