[bug-notifications] [alternatives 0004538]: Symbolic links not created in new sparse-root zone

Mantis Bug Tracker noreply at opencsw.org
Fri Sep 3 01:21:50 CEST 2010


A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4538 
====================================================================== 
Reported By:                gadavis
Assigned To:                phil
====================================================================== 
Project:                    alternatives
Issue ID:                   4538
Category:                   regular use
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2010-08-31 22:19 CEST
Last Modified:              2010-09-03 01:21 CEST
====================================================================== 
Summary:                    Symbolic links not created in new sparse-root zone
Description: 
There appears to be a bug in the alternatives mechanism when creating a new
sparse-root zone on Solaris 10 systems.

I have a global zone with CSW alternatives, CSWneon, CSWsudo, and
CSWsudo-common installed. The alternatives mechanism has registered the
symlinks in the right locations and alternatives --display neon and
alternatives --display sudo work as expected.

If I then create a new non-global zone with the default inherited paths
(your typical sparse-root zone), alternatives --display whatever shows the
correct paths listed, but the symlinks are not there.

After zone creation, I have to manually force the alternatives mechanism
to install the needed symlinks by running a shell loop:

for d in `ls /opt/csw/share/alternatives`; do 
	alt=`basename $d`; 
	alternatives --auto $alt; 
done

Note that if I uninstall CSWsudo inside the zone and then re-install it,
the alternatives mechanism works as expected. It's only upon initial zone
creation that the alternatives symlinks do not get created.
====================================================================== 

---------------------------------------------------------------------- 
 (0008247) gadavis (developer) - 2010-09-03 01:21
 https://www.opencsw.org/mantis/view.php?id=4538#c8247 
---------------------------------------------------------------------- 
I can see where the class action scripts could cause problems in this
mixed-mode when packages are added and removed.

However, just to be clear, no further pkgadd commands were run in either
the global zone or non-global zone after the zone was installed with
"zoneadm -z whatever install"

It's worth determining what exactly happens with the class action scripts
when zoneadm install is run and the list of currently installed packages is
duplicated to the zone.



More information about the bug-notifications mailing list