test

Sun Update Connection - Enterprise Release Notes

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