http://defect.opensolaris.org/bz/show_bug.cgi?id=10160
amaguire <alan.maguire at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alan.maguire at sun.com
Status|NEW |ACCEPTED
--- Comment #3 from amaguire <alan.maguire at sun.com> 2009-07-21 07:21:17 ---
(In reply to comment #2)
> what I means is:
> 1. for conditional loc, its "enabled" property failed to show its correct
> status.
> 2. for conditional loc, it can not set the conditions to "other" loc is
> active,
> since only one loc can be actived.
I'm a bit confused here, but the first thing to mention is that in this case
loc2 should actually continue to be active despite the "nwamadm disable". This
is because when you disable a conditional loc, all you're doing is saying is "I
don't want this location enabled all the time, just when its conditions are
met". Since its conditions are still met, it stays online. The "entity is in
incorrect state" message is confusing however.
Also that's a good point about location conditions - it doesn't make sense to
support an "another-loc is active" condition for locations, since only one
location can be active at once. We should disallow this activation condition
for locations at the library level. It makes sense to continue to support
"another-enm is active" for locations and enms (and indeed "another-loc is
active" for enms).
So it seems like there's two issues here:
- ensure the disable succeeds without error message
- disallow locations from specifying "another-loc is active"
Does that sound right?
--
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.
