http://defect.opensolaris.org/bz/show_bug.cgi?id=10368
--- Comment #4 from Anurag S. Maskey <Anurag.Maskey at Sun.COM> 2009-08-04
19:05:31 ---
(In reply to comment #3)
> The reason is that nwamd will take several seconds, say 3 secs, to settle now
> when the case executes 'nwamcfg destroy -a', otherwise the output of 'nwamadm
> list' looks like:
> TYPE PROFILE STATE
> ncp User uninitialized
> ncp Automatic uninitialized
> loc NoNet uninitialized
> loc Legacy uninitialized
>
> so the testing will fail.
>
> I guess this is because the latest modification makes the action like 'destroy
> -a' will refresh nwamd, and nwamd needs time to refresh.
nwamd maintains copies of all objects as it is running. Any persistent change
in objects (eg, commit, destroy) sends events to nwamd to update that object's
state. This has always been the case. Could the tests have a "wait" time
before it checked the states (similar to waiting when doing "nwamadm enable -p
ncp {Automatic|User}")?
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
