test

Sun Update Connection - Enterprise Release Notes

Chapter 1 Known Issues and Workarounds

This chapter includes information about issues with the Sun Update Connection – Enterprise product and workarounds for these issues. Known issues for 1.0.0, 1.0.1, 1.0.2, and 1.0.3 releases are listed in this chapter. If an issue is fixed in a specific release, it is noted. For a list of fixed issues by release, see Chapter 3, Issues Fixed and New Functionality.

This chapter covers the following issues:

General Issues

This section describes issues that you might encounter while using Sun Update Connection – Enterprise software. For issues introduced in a specific release, see Release-Specific Issues.

BMI Is Unavailable

Description:

The bare metal installation server (BMI) module is not available.

Workaround:

If you are interested in creating and using a BMI server with Sun Update Connection - Enterprise, please contact your Sun Sales representative.

Agent Installation Script Can Fail on All Versions of Solaris (#6482852)

Description:

Agent installation fails on Solaris with:

./Install: not found

Cause:

The agent installation script requires the 'bash' shell which is not a standard shell on Solaris.

Workaround:

Install the SUNWbash package from your Solaris installation media.

Note –

The bash shell is also required to be able to run the agent.

Missing Agents for RH AS_2.1 and ES_2.1 in Sun Update Connection - Enterprise (#6456194)

Description:

Sun Update Connection - Enterprise does not provide agents for RH AS_2.1 and ES_2.1.

Workaround:

New agents are not available at this time.

"Internal Query Failed" Message When Running Job on New Installation (#6470383)

Description:

On a fresh installation of Sun Update Connection - Enterprise, if the first job created uses any policy other than "Ask Me", the user will get an error when running the job: "internal query failed". This problem will also occur when running BMI, which uses pre-defined policy.

Workaround:

Create and run a job which uses a policy of "Ask Me". Subsequent jobs will then run without displaying the above error, regardless of the policy they use.

SDS Appears to Download Content That is Already Cached (#6456161)

Description:

Sometimes the System Dependency Server appears as if it is downloading content that is already cached and available to the agent.

Workaround:

This is a reporting error in the user interface. Content that is available in the cache is not downloaded again.

Scheduling Recurring Jobs (#6456169)

When scheduling a recurring job, you must select the specific day or days when you specify the Day of Week or Day of Month.

Downloading Solaris Components (#6459005)

When you plan to download Solaris components, such as patches, ensure that the following utilities are installed on the SDS machine:

If any of these utilities are missing, the download of Solaris patches might fail, although the error logs do not always indicate that a missing utility was the cause.

S390 Channels and VM Cloning Are Not Supported

S390 channels and VM cloning are not yet supported in Sun Update Connection – Enterprise or BMI.

Release-Specific Issues

The following issues are release-specific and have been fixed in subsequent releases:

1.0.2 – Upgrade to the 1.0.2 Release Might Fail

Description:

If you previously upgraded from Sun Update Connection - Enterprise 1.0 to 1.0.1, upgrading from the 1.0.1 release to the 1.0.2 release can fail.

Note –

This issue is fixed in the 1.0.3 release.

Workaround:

Remove the directory: /usr/local/uce/engine/db/data and then re-run the 1.0.2 installer.

1.0.0 – Console Fails to Access the Sun Update Connection – Enterprise Documentation

Description:

When you select UCE Help from the Help menu, a browser window opens, but it cannot access the Sun Update Connection – Enterprise documentation on docs.sun.com.


Error: The requested item could not be found.
Note –

This issue is fixed in the 1.0.1 release.

Workaround:

Update the link to the Sun Update Connection – Enterprise documentation in the uce.rc file.

Caution – Caution –

Do not change any other lines in this file!

    Follow these steps:

  1. Login as superuser on the system where you installed the console.

  2. Close the console.

  3. Find the uce.rc file.

    • Linux: /usr/local/uce/console/bin/uce.rc

    • Windows: C:\uce_console\bin\uce.rc

  4. Change the online_PDFs_url line in uce.rc.

    The final part of the referenced URL is incorrect. You must change 11561.1 to 1561.1.

    When changed, the line should be the following:


    ( all ) ( invisible.gui.__general.online_PDFs_url, "http://docs.sun.com/coll/1561.1" );

  5. Restart the console to load the change.


    # uce_console

Support Issues

This section describes issues that concern Sun Update Connection – Enterprise support.

Latest Sun Update Connection – Enterprise Knowledge Channels and System Requirements

The knowledge channels available for Sun Update Connection – Enterprise are listed in Sun Update Connection - Enterprise 1.0 Quick Start Guide: Getting Started. The latest list can also be found at http://www.sun.com/service/sunupdate/enterprise/knowledge.html.

The system requirements for Sun Update Connection – Enterprise components are available in Sun Update Connection - Enterprise 1.0 Quick Start Guide: Getting Started. The latest requirements can also be found at http://www.sun.com/service/sunupdate/enterprise/specs.html.

Upgrade Issues

This section describes issues that are related to upgrading the product from Sun Aduva OnStage to Sun Update Connection – Enterprise.

Upgrading From Sun Aduva OnStage 439 to Sun Update Connection – Enterprise (#6456170)

Description:

Existing channels on Sun Aduva OnStage 439 that do not have any locally registered components require that you perform a post-upgrade check.

Workaround:

    After you complete the upgrade, do the following:

  1. For each channel, check that the following file exists:


    /usr/local/uce/server/public/config_files/distribution/.client_rpms_info.xml

  2. If this file does not exist, it must be created and should contain the following lines:


    <?xml version="1.0.2" encoding="UTF-8"?>
<NCO_LIST>
</NCO_LIST>

Missing Solaris Packages After an Upgrade From Sun Aduva OnStage 439 to Sun Update Connection – Enterprise (#6456178)

Description:

Following an upgrade from Sun Aduva OnStage 439 to Sun Update Connection – Enterprise, Solaris packages might not be available.

Workaround:

If the Solaris packages are not available, upload them to the System Dependency Server.

    For each of the Solaris channels (Solaris 8, Solaris 9, and Solaris 10), do the following:

  1. Create a temporary directory for uploading.


    # mkdir /tmp/files_to_re_upload

  2. Copy the files to your upload directory.


    # cp /usr/local/uce/server/public/private_blobs/Solaris-channel/*.blob \
/tmp/files_to_re_upload

  3. Access the file upload page in a web browser.

    Go to https://SDS-hostname:8002/upload.html.

    1. Specify the channel.

    2. Specify the path to the temporary upload directory.

    3. Specify the user name and password to start the upload.

    4. Click Submit.

  4. Remove the temporary directory you created for uploading.


    # rm -rf /tmp/files_to_re_upload

Missing Credentials After an Upgrade From Sun Aduva OnStage 439 to Sun Update Connection – Enterprise

Description:

The credentials you entered to access software directly from a vendor, such as for the Solaris patches, are not saved as part of the backup process.

Workaround:

Add these credentials after the upgrade is complete by using the Sun Update Connection – Enterprise Authentication window.

Missing Cached Public Components After an Upgrade From Sun Aduva OnStage 439 to Sun Update Connection – Enterprise

Description:

The cached public components that were downloaded with Sun Aduva OnStage are not saved as part of the backup process.

Workaround:

Download the cached public components after the upgrade is complete.

Attempts to Install Solaris Packages Fail After an Upgrade From Sun Aduva OnStage 439 to Sun Update Connection - Enterprise (#6464386)

Description:

When attempting to install Solaris packages, the package install fails with an error regarding the parameter CLIENT_BASEDIR.

Workaround:

    Do the following:

  1. Copy the UCE agent tar ball to the host.

  2. Remove the ADVagent package.

  3. Unpack the UCE agent tar ball.

  4. Install the UCE agent.

Download the cached public components after the upgrade is complete.

Job Logs not Available After Upgrade From Sun Aduva OnStage 439 to Sun Update Connection - Enterprise (#6454745)

Description:

After the upgrade, job logs from the previous release are no longer available

Workaround:

Backup the logs before the upgrade and restore them after the upgrade.

Before the upgrade: Backup the OnStage agent log directory content located at: /opt/local/aduva/director_agent/log

After the upgrade: Restore the saved data into the UCE agent log directory, located at: /opt/local/uce/agent/log

Configuration Issues

This section describes issues that you might encounter while configuring your Sun Update Connection – Enterprise environment.

Setting the Default Kernel for the Linux Knowledge Channel (#6456009)

Description:

If you are using the Linux knowledge channel, you cannot use Sun Update Connection – Enterprise to set the default kernel.

Note –

This issue is fixed in the 1.0.2 release.

Workaround:

Instead, you must set the default kernel manually.

Enabling Log Rotation in the Sun Update Connection – Enterprise Proxy (#6455904)

To enable log rotation in the Sun Update Connection – Enterprise Proxy, manually install a copy of the Log_rotation configuration file on the proxy.

The file is on the server at /etc/logrotate.d/director_server.

Local Solaris Patches That are Not Available on SunSolve are Not Included in the Knowledge Base (#6456168)

Local patches that are not available on SunSolveSM and that are distributed as part of a package are not included in the Sun Update Connection – Enterprise knowledge base.

In these cases, the Sun Update Connection – Enterprise agent might not have installed a needed patch given that the (needed) patch it intends to install is obsoleted by an already installed (local) patch.

For example, if PKG-1 installs Patch-Q (local patch not part of knowledge base), Sun Update Connection – Enterprise then recommends Patch-P. However, Patch-Q obsoletes Patch-P. In this case, UCE (correctly) fails to install the obsoleted patch Patch-P.

When using Solaris Baselines, add the obsoleted patch, Patch-P, to the black list.

Cookies are Expired When Downloading Red Hat Components (#6456196)

Description:

When you attempt to download Red Hat components from the Red Hat Network, the download fails because the cookies have expired.

You might see this problem when you use other web clients, such as Konqueror.

Cause:

This problem occurs when the system clock on your SDS is not set to the current time, but is set forward to a time in the future. Cookies created on your system might be expired.

Workaround:

Ensure that the system clock on the SDS machine is set to the current time. The system clock must be set to the current time because it is used for cookie validation.

Sun Update Connection – Enterprise Application Issues

This section describes issues that you might encounter when using Sun Update Connection – Enterprise applications.

CLI Fails to Run (#6456099)

Description:

Sometimes the CLI fails to run.

Workaround:

    Do the following:

  1. Log in to the console as the same user that you used to access the CLI.

    The console should indicate that this user is already logged in.

  2. Confirm this message and then exit console.

    CLI will now be accessible.

Console Sometimes Hangs (#6456138)

Description:

Sometimes the console hangs if open for a long time.

Workaround:

Close the console when not is use or close the console occasionally when you use it for a long time.

The system on which you run the console should have at least 1 Gbyte of memory.

Console Can Hang When Preferences Changed (#6464925)

Description:

If the console preferences are changed, and then an attempt is made to change them for a second time, the console can hang.

Workaround:

Kill the console and restart it.

Job Can Hang When "Remote Hosts" is Used to Upload RPM (#6466850)

Description:

If the "Remote Hosts" option is used to upload a file, and the remote host goes offline during the upload, the job remains stuck in the console, even after the remote host restarts.

Workaround:

Kill the console and restart it.

Copying Non-Certified Objects Between Channels (#6456000)

If you want to copy Non-Certified Objects (NCOs) between channels, use the scriptable API.

Managed Host Issues

This section describes issues that impact Sun Update Connection – Enterprise managed hosts.

Additional RPMs Need to be Installed to Use BMI on SuSE 9.2 (#6456148)

When using Bare Metal Installation with the Sun Update Connection – Enterprise System Dependency Server on SuSE 9.2, you must download and install the following RPM:


ftp://ftp.suse.com/pub/suse/i386/9.2/suse/i586/python-mysql-1.1.1-2.1.i586.rpm

Solaris Agent Disconnects and OpenSSL PRNG not seeded Error Occurs

Description:

After running a job on a Solaris agent and after performing the reboot job, the Solaris agent becomes disconnected. Also, the following error message appears several times in the debug log on the agent:


358:error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not
seeded:md_rand.c:512:You need to read the OpenSSL FAQ,
http://www.openssl.org/support/faq.html
Cause:

This problem is described on the OpenSSL web site at http://www.openssl.org/support/faq.html#USER1.

Workaround:

If you are using a Solaris 8 system, add the /dev/urandom and /dev/random devices by installing patch ID 112438 (SPARC®) or patch ID 112439 (x86). These patches are available from Patchfinder at http://sunsolve.sun.com.

The Solaris 9 software includes these devices by default.

To get /dev/random support for earlier Solaris versions, see Sun's statement at http://sunsolve.sun.com/search/document.do?assetkey=1-25-27606-1.

The SUNWski package is available in patch ID 105710.

Agent Uninstall Fails if SDS is Offline (#6460566)

Description:

The agent communicates with the SDS when asked to exit. If the SDS is offline or inaccessible, the agent will not be able to be stopped normally and thus cannot be uninstalled.

Workaround:

Kill the agent manually if it hangs.

Reboot Notification Flags are Not Set When Host is Marked as Pending Reboot

Description:

    When a user chooses not to perform an immediate reboot of a host, the Pending Reboot is indicated by the UCE console twice:

  1. In the Host progress dialog.

    There is a line on the Host's TODO list saying Remember to reboot

  2. In the Inventory window.

    The inventory window displays the host list on the left and the components tree on the right.

As part of the components tree there is a specific root category named Notifications. Within this category there are two components: Reboot and Reboot Reconfigure. These two components are normally marked as (installed) when the selected host has 'Pending Reboot'. However, this indication is not working. The (installed) indication is not shown.

Workaround:

This does not affect the operation of the application.

Documentation Issues

This section describes issues that affect the Sun Update Connection – Enterprise documentation.