Sun Update Connection - Enterprise Release Notes

Chapter 3 Issues Fixed and New Functionality

This chapter includes information about issues fixed and new features found in the Sun Update Connection - Enterprise, release 1.0.1, 1.0.2, and 1.0.3.

Issues Fixed in the 1.0.3 Release

The following issues are fixed in the 1.0.3 release:

6478514

Agent core dumps

6487546

Limit agent's core dump size

6476975

Agent uses too much memory

6478091

In any task failure in single user mode There should be a reboot+reconfigure // just in case

6478337

In any case have Reboot+reconfigure in single user mode.

6485567

Double reboot - in single user mode

6476869

Deploy a profile with baselines + post actions

6468073

UCE 1.0 upload.html never attached components

6484752

Agent core dumps after dowload fails

6487541

Incorrect messages in log file if download fails

6487716

Postgres optimisations lost during upgrade from UCE 1.0.1

6488794

Seeker failure should be reported

6488762

Inventory is NOT sent to console

6487543

Osiris table had bad query

6480552

No rules with huge vtree

6485365

Upgrade from 1.0.0 to 1.0.2 causing later upgrade to 1.0.3 to fail

6488733

Old osiris table

6489768

Postgres env problem

6490125

Postgres table create failure

6488762

Get hosts inventory in chunks of (50) failed for a customer because of msg size limit in comm_system

6487760

BMI tar ball packaging

6488178

File descriptor leakage

6490127

No error message reported if downloaded blob is zero size

6489367

Failed to add Solaris x86 agent package

Issues Fixed in the 1.0.2 Release

The following issues are fixed in the 1.0.2 release:

6456009

Setting the default kernel for the Linux knowledge channel

6449

Some of the Contextual Online Help is Displayed Incorrectly (#6449)

6463826

Legacy license file (license.pdf) still in customer build

6470485

Console on-line help is invalid

6475328

Upgrade fails (can't login to console) if reporting has been used

6478514

Agent core dumps if bad data is written to its listener port

6478116

Engine installation fails on mainframe Linux

6478241

Editing the kickstart file for Solaris provisioning causes the creation of the wrong password.

6478511

Profile sent from BMI created an invalid policy

6456012

Problem with BMI URLs on sles8 and suse 9.0

6456037

BMI chooses wrong inetboot for Solaris

Issues Fixed in the 1.0.1 Release

The following issues are fixed in the 1.0.1 release:

3976

Hosts belonging to deleted task are "remembered" when a new task is created

5642

Jobs should be executed in order of their priority

6461

BMI for Solaris x86 does not work

6519

Issues with VM Cloning

6424709

Cannot download any rpm on Itanium machines

6427151

Solaris 10 SPARC agent core dumps when downloading the SUNWfreeware packages

6456095

Failed to install BMI plugin pkg on RH AS3 64bits on AMD64

6456189

The default for the "Deploy not standard patches " should be set to false by default

6456193

Online help files are not available from Help-->UCE_Help

6456694

Solaris agent fails in single-user mode if /opt is not in the root partition

6470485

Console Fails to Access the Sun Update Connection – Enterprise Documentation

New Functionality in the 1.0.1 Release

The following new functionality is in Sun Update Connection - Enterprise 1.0.1:

Replacement of MySQL Database Server with PostgreSQL

Sun Update Connection - Enterprise 1.0.1 replaces the MySQL database server in the SDS with a PostgreSQL database server. Every effort has been made to make the administration and operation of the PostgreSQL database server transparent to users.

The upgrade process from Aduva OnStage 439 or Sun Update Connection - Enterprise 1.0.1 will automatically migrate existing data from the MySQL database to the new PostgreSQL database instance.

Enhancements to Solaris Patch Handling

Patches that are bundled with a Solaris package, and are NOT available through Sunsolve used to be ignored by the agent seeking mechanism.

This caused:

The new release of Sun Update Connection - Enterprise introduces an optimization in this area, such that whenever a patch, which is unknown to the application, is detected as installed, the agent tries to mark the closest patch (with a lower revision in the vtree) as implicitly installed. In this case at least the obsoleted revisions will be marked correctly and the resolve/reports will generate the correct results.