Bugzilla – Bug 5012
sys-unconfig-config no networking, networking comes up anyway
Last modified: 2008-12-03 16:07:48 UTC
You need to log in before you can comment on or make changes to this bug.
sys-unconfig was run to wipe all configuration data. When the system was rebooted, networking was explicitly turned off (in the sysidtool panels). As the system came up, the wireless and wired devices were automatically reconnected. Is this the behavior that should occur?
Could the submitter report the output of 'svcs network/physical' on the system when it comes up with network interfaces configured?
I don't think sys-unconfig was ever updated to support NWAM, which is on by default in the OpenSolaris distribution. I'm not even sure that it should be updated that way -- it doesn't seem wrong to me that NWAM (which is dynamic configuration, not static) starts up and does its thing normally after a sys-unconfig reboot. This looks like "not a bug" to me.
Please refer to 6553976 for some history on this. In particular, the evaluation: The immediate problem is that sys-unconfig does not restore the old, familiar behavior, but it has been advertised as a way to do so if SXDE users don't like the new configuration assumptions made. Therefore, sys-unconfig should disable the nwam service, which is one of those new configuration things introduced in SXDE, and enable network/physical:default. A note to the user that it's doing so would also be useful, as changing the state of an smf service might not be considered part of reverting the system to a blank slate. My concern is that, based on this bug report and some other comments I've seen on various mailing lists, the sys-unconfig behavior has changed (or been broken), and nwam is no longer being disabled. While the behavior put in place with the fix for 6553976 would not be my top choice, I think it at least be consistent until we can agree on a better approach.
jack@opensolaris:~$ svcs network/physical STATE STIME FMRI disabled 13:23:41 svc:/network/physical:default online 13:23:42 svc:/network/physical:nwam
My understanding matches that of Renee - I thought at some point sys-unconfig(1M) disabled network/physical:nwam but perhaps I'm mistaken. I've added Ethan to the Cc as he would know.
sys-unconfig was never updated to know about nwam, or to touch either instances of the network/physical service for that matter. If one uses sysidtool/sys-unconfig, one has to manually disable nwam if its enabled.
I don't think Ethan's comment is entirely correct. The first part is: sys-unconfig itself was not updated to know about nwam. But the fix for CR 6553976 added a handler for the -u flag to the net-nwam start method, which is called on sys-unconfig. This handler sets the general/enabled property of the network/physical:nwam service instance to false, and that of the default instance to true, so that on reboot, nwam will be disabled and network/physical:default (which uses the configuration created during sys-net-config) will be enabled. This change was integrated into build 64, and as far as I know has worked since then; but I'm hearing reports (this bug being one of them!) that it's not working in the 2008.11 release candidates. Ethan, can you shed any light on this? Any ideas on what might have changed? As far as I can tell, the code in the net-nwam start script has not changed.
Nothing has changed in the sys-unconfig code that would change its invocation of net-nwam method with -u. There's a log file that might at least tell us if something went awry. Vicki, can you attach /var/log/sysidconfig.log
As a datapoint, I just tried a sys-unconfig while nwam was enabled on a system running nevada build 101 (*not* opensolaris); I found that, as expected, nwam was disabled and net/physical:default was enabled on reboot. The sysidconfig.log file showed net-nwam being called: Executing Configuration Applications at: Mon Nov 17 16:26:42 2008 Executing config app: /usr/sbin/sysidkbd Executing config app: /usr/sbin/sysidpm Executing config app: /lib/svc/method/sshd Executing config app: /lib/svc/method/net-nwam Executing config app: /usr/lib/cc-ccr/bin/eraseCCRRepository Executing config app: /usr/lib/scn/bin/cleanup-scn-base Completed Executing Configuration Applications at: Mon Nov 17 16:26:43 2008 Executing Configuration Applications at: Mon Nov 17 16:30:14 2008 Executing config app: /usr/sbin/sysidkbd Executing config app: /usr/sbin/sysidpm Executing config app: /lib/svc/method/sshd Executing config app: /lib/svc/method/net-nwam Executing config app: /usr/lib/cc-ccr/bin/eraseCCRRepository Executing config app: /usr/lib/scn/bin/cleanup-scn-base Completed Executing Configuration Applications at: Mon Nov 17 16:32:54 2008 Vicki, it would be good to see what this looks like on your opensolaris system.
Created an attachment (id=964) [details] sysidconfig.log file from the M10 with the problem Here's the sysidconfig.log that you requested!
Created an attachment (id=965) [details] sysidconfig.log file from the M10 with the problem Here's the sysidconfig.log that you requested! (BTW -- you're seeing a logfile that was created based on rc1.5.)
Your sysidconfig.log file looks fine. I just did a sys-unconfig on a rc1.5 system and noticed that upon boot up after the sys-unconfig, nwam is online and physical:default is offline, so something is going on here in osol rc1.5 I'll investigate further.
(In reply to comment #12) > Your sysidconfig.log file looks fine. Actually, I didn't look at your log file close enough. It seems that upon a run of sysidconfig (possibly the unconfig while the system was going down), the net-nwam method wasn't found: Executing config app: lib/svc/method/net-nwam sys-unconfig: Warning: Application Not Found Completed Executing Configuration Applications at: Mon Nov 17 18:20:44 2008 I'm able to reproduce this.
In Nevada, the list of applications in /etc/.sysidconfig.apps are absolute paths; however, in OpenSolaris they're not. sysidconfig tries to find them wrt the cwd of where you run sys-unconfig (during the unconfig time when the system is going down), so if you happen to not be in "/", if fails to find the applications. This probably hasn't been noticed before because most of the applications listed in .sysidconfig.apps do nothing with -u; net-nwam and sysidpm are two that I can see that do. The workaround is to cd "/" before running sys-unconfig
The fix is in libict_pymod/ict.py::add_sysidtool_sys_unconfig_entries() where we hack in entries into the /etc/.sysidconfig.apps file. The entries need to be changed to be absolute paths.
*** Bug 4901 has been marked as a duplicate of this bug. ***
(In reply to comment #7) > the fix for CR 6553976 added a handler for the -u flag to the net-nwam > start method, which is called on sys-unconfig. > > This change was integrated into build 64, and as far as I know has > worked since then; but I'm hearing reports (this bug being one of > them!) that it's not working in the 2008.11 release candidates. Note that the fix for 6553976 was an addition to the SUNWcsr postinstall script - IPS doesn't have postinstall scripts, so fixes like that will need to be re-worked for OpenSolaris releases.
Fixed in changeset c15961301ffd08ea3efd596471c74f2508be11ca