http://defect.opensolaris.org/bz/show_bug.cgi?id=10453
Summary: nwamcfg destroy -a silently fails to destroy the User
ncp if it was previously active
Classification: Development
Product: nwam
Version: unspecified
Platform: ANY/Generic
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: ON library
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: John.Leser at sun.com
QAContact: nwam-dev at opensolaris.org
So, I have a User ncp defined and active:
bash-3.2# svcadm enable nwam
bash-3.2# nwamadm list
TYPE PROFILE STATE
ncp User online
ncu:phys e1000g0 online
ncu:ip e1000g0 online
ncp Automatic offline
loc Automatic online
loc NoNet offline
loc Legacy offline
bash-3.2# nwamcfg export
create ncp "User"
create ncu phys "e1000g0"
set activation-mode=prioritized
set priority-group=0
set priority-mode=shared
end
create ncu ip "e1000g0"
set ip-version=ipv4
set ipv4-addrsrc=static
set ipv4-addr="10.8.57.93/24"
end
end
I want to stop nwam, delete the ncp and rebuild it, then start nwam back up
again:
bash-3.2# svcadm disable nwam
bash-3.2# svcs | grep nwam
bash-3.2# nwamcfg destroy -a
bash-3.2# echo $?
0
bash-3.2# nwamcfg export
create ncp "User"
create ncu phys "e1000g0"
set activation-mode=prioritized
set priority-group=0
set priority-mode=shared
end
create ncu ip "e1000g0"
set ip-version=ipv4
set ipv4-addrsrc=static
set ipv4-addr="10.8.57.93/24"
end
end
Here, the User ncp doesn't get deleted if it was active when nwam was stopped.
This limitation is causing some problems in the event tests, which used to do
the above sequence without problems. It could be worked around by activating
the Automatic ncp prior to stopping nwam and doing nwamcfg destroy -a, but this
will make everything take longer and have more ncp switches than necessary
during testing.
I'm definitely seeing this issue with nwam1-build:2009-08-04, but it's probably
been in the gate for a week or so.
--
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.
