http://defect.opensolaris.org/bz/show_bug.cgi?id=10805
amaguire <alan.maguire at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CAUSEKNOWN
CC| |alan.maguire at sun.com
AssignedTo|nwam-dev at opensolaris.org |alan.maguire at sun.com
--- Comment #2 from amaguire <alan.maguire at sun.com> 2009-08-20 16:54:32 UTC
---
The problem here is that the script execution associated with enm deactivation
(that occurs on the way to destroying the object) fails, and as a consequence
we go to maintenance, and don't destroy the enm object. Its handle is still
valid (since it was read prior to the destroy), and mdb shows it's still on the
object list.
I can reproduce this problem with an ENM with failing scripts, but notice it
doesn't happen with an ENM that has valid scripts - if the stop script doesn't
exist or fails we hit this error condition. The solution is not to set
maintenance state on destroy (which we can determine from the aux state) in
nwamd_enm_activate_deactivate_thread().
--
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.
