test

Sun Connection 1.1 Release Notes

Agent Issues

Fail to Register All NCOs (CR 6565602)

Description:

A bug in the sed utility ( /usr/bin/sed ) during the pkg_seeker.sh process causes failures in the registration of the packages.

Workaround

Install patch #110165-05 or higher.

The patchadd -G Command is Used Incorrectly (CR 6533814)

Description:

This error occurs in Sun Connection 1.1.0 and 1.1.1.

When the agent is installing patches on Solaris 10 in the global zone, it only uses the SUNW_PKG_ALLZONES package parameter to decide whether to use the patchadd command, or the patchadd -G command.

The /var/sadm/install/gz-only-packages file contains a list of packages that were installed on the systems using the pkgadd -G command and that should not be propagated to any local zone. Sun Connection should check the /var/sadm/install/gz-only-packages file to decide which patchadd command to use.

If a package is not in the package list in the /var/sadm/install/gz-only-packages file, it should be installed with patchadd command, not the patchadd -G command. The current agent design incorrectly uses only the patchadd -G command to update the /var/sadm/install/gz-only-packages file.

Results:

Once the /var/sadm/install/gz-only-packages file is updated with the patchadd -G, you cannot properly create a new zone because not all of the listed packages will be propagated into the new zone. This will result in a broken zone,

The patchadd Command Requires You to Manually Mount Zone Roots For Single User Patches (CR 6548606)

Description:

For patches requiring application in single user mode, that alter ALLZONES packages, the patchadd is unable to apply the patch if zone roots are not on the / or /var filesystems.

Workaround:

Before you run a patch job, run the mountall -l command to ensure local filesystems are mounted.

Local Zone Patching With Mounted Partitions

Description:

If a zone mount command fails, patches appear to be installed in multi-user mode. When the zone mount fails, the agent script exits and the system comes up in multi-user mode. The agent restarts and attempts to run the rest of the job. If patches are applied to all zones using the patchadd command, the patches are not added. If patches are applied using the patchadd -G command, the patches are added, but the system does not reboot.

Workaround:

Before you run a patch job, run the mountall -l command to ensure local filesystems are mounted.

Edit the /etc/rcS.d/S90agent file and remove exit 1 from line 130.

Read-Only Users Can Deploy Jobs (CR 6553436)

Description:

In the 1.1.0 and 1.1.1 releases, read-only users can deploy jobs from the send job option in the Report windows. The deploy button is not disabled in the Report output pages.

Agent Installation Might Fail When Logged Into a Zone Using zlogin (CR 6513395)

Description:

When trying to install the agent package in a non-global zone, the user may see the following and the installation will fail:

./Install

/uce_agent/scripts/agent_main: test: unknown operator 80

Cause:

The installer needs to know the size of the window in which it is running in order to be able to correctly display the installation status. However, when logging into the zone's console using zlogin, this does not pass the number of rows and columns from the window into the zone's login shell as a remote login application such as ssh, telnet, or rlogin would, so the installer fails.

Workaround:

Use a remote login application such as ssh, telnet, or rlogin to login to the zone and run the installation. This correctly sets the terminal rows and columns from the window in which it was launched. Alternatively, use the stty command to set the correct number of rows and columns once you login with zlogin.

Agent Installed in a Non-Global Zone Fails to Register (CR 6511890)

Description:

If an agent is installed in a non-global zone on a system before an agent is installed in the global zone, the agent in the non-global zone will fail to register and a message in the log file will display: ?Host/Group not found?.

Workaround:

Install an agent in the global zone. The non-global zone agent will successfully register after the global zone agent has registered.

Installation of Packages or Patches on Sparse Zone Fails (CR 6508687)

Description:

When attempting to install a package or patch on a sparse zone, the installation will fail if the package or patch needs to add content to /usr directory.

Cause:

This is not a bug in the product, but a feature of zones. Sparse zones have a copy of /usr provided by the global zone which is mounted read-only. Installation of any package (by Sun Connection or manually) which needs to place content in /usr will fail because pkgadd is unable to write to /usr

Workaround:

Add the package to the global zone or use a full zone instead of a sparse zone.