Sun Update Connection 1.0.4 Now Available

The Sun Update Connection Client, Version 1.0.4 is now available as software update121118-05 (SPARC version located at http://sunsolve.sun.com/search/document.do?assetkey=1-21-121118-05-1) or 121119-05 (x86 located at http://sunsolve.sun.com/search/document.do?assetkey=1-21-121119-05-1). This client software update is a minor maintenance release that accumulates numerous fixes that have been reported in previous versions. Improvements introduced in the version 1.0.4 client that are worthy of note include:

<ul>

<li>The Update Connection client has been modified to be fully operational in the global zone on systems configured with Solaris 19 Zones.Support for patching specific non-global zones will be available in a future update. (6302734)</li>

<li> The 'smpatch download' command has been modified to retrieve any revision of a patch whether current or obsolete. This capability allows us to use smpatch as a complete functional replacement for ftp as a general patch download tool. (6283475)</li>

<li>Similarly, the 'smpatch download" command can also retrieve patch README files for any revision of a patch, current, obsolete, and even withdrawn. (6283475)</li>

<li>The Update Connection desktop notification/launcher icon is disabled by default for Sun Ray users who should not have patching privileges (6338619)</li>

<li>The Update Manager will report "Pending restart" instead of "Successful" on for patches that require system restart (6338511)</li>

<li> Update Connection clients Update Manager and smpatch have been made more tolerant of delivery server hangs (6335197)</li>

<li>Minor performance improvement were achieved by removing unnecessary internal calls to "smpatch list" at the end of patch installation (6336195)</li>

<li>We have corrected the case where a Solaris host appears as a managed asset in the hosted web app but could not be analyzed or updated. All systems that appear in the hosted web app can now be analyzed and updated. (6341454)</li>

</ul>

Updates to the Sun Update Connection server-side "Hosted" application and infrastructure will also be deployed on February 25 to add infrastructure changes needed to support the My Sun Connection portal. In addition, several minor user interface enhancement have been made to improve ease-of-use. No new features are being added to the Hosted application in this release.

For a complete list of the defects corrected in this release please

refer to the patch README file for this patch. Additionally, the Sun Update Connection Release Notes have been updated (see http://docs.sun.com/source/916-1619/index.html). Note also that this update includes fixes that were delivered in prior releases of the Sun Update Connection client software. By installing this update you may be getting fixes that were previously available but not present on your system.

Thank you,

Kayo Granillo

kayo.granillo@sun.com

[3098 byte] By [kayo_granillo] at [2007-11-26 6:05:31]
# 1

Whohoo.

It seems to work.

I can finally retire my do_patches script.

Now all I need you to fix is the speed of patching zoned machines.

Last time I tried to patch a machine with 8 zones that was only a month behind in its patches, it took about 9 hours to do a patching run. And 3 hours of that was in the "critical" phases where services are supposed to be shut down..

robertcohen at 2007-7-6 13:33:01 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2

Looks like I spoke too soon.

First time Ive run it on a zoned machine with patches to install.

And both the "delayed" patches fail to install.

They both install fine on a non zoned machine.

Console just shows

Installing update 119850-13 Failed

Installing update 119715-10 Failed

Where should I look for more informative logs?

robertcohen at 2007-7-6 13:33:01 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 3

I found this logfile

less /var/sadm/spool/disallowed_patch_list_report

STATUS INSTALL BEGIN 119850-13

Transition patching (-t option) is not supported in a zones environment.

STATUS INSTALL END 119850-13 INSTALL.1

STATUS INSTALL BEGIN 119715-10

Transition patching (-t option) is not supported in a zones environment.

STATUS INSTALL END 119715-10 INSTALL.1

robertcohen at 2007-7-6 13:33:01 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 4
Can we confirm that you are trying to patch the Global zone?
ForumModerator at 2007-7-6 13:33:01 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 5
Yess, running "smpatch update" in the global zone.Then reboot with "shutdown -y -g0 -i6"
robertcohen at 2007-7-6 13:33:01 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 6
Bug # 6362146 has been raised for this issue
ForumModerator at 2007-7-6 13:33:01 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 7

> I found this logfile

>

> less /var/sadm/spool/disallowed_patch_list_report

> STATUS INSTALL BEGIN 119850-13

> Transition patching (-t option) is not supported in a

> zones environment.

> STATUS INSTALL END 119850-13 INSTALL.1

> STATUS INSTALL BEGIN 119715-10

> Transition patching (-t option) is not supported in a

> zones environment.

> STATUS INSTALL END 119715-10 INSTALL.1

I have removed the -t in /etc/rcS.d/S51installupdates in the line

$PATCHADD -t $BACKOUT_PARM $DEFERRED_DIR/$PATCHID.jar.dir/$PATCHID >> "$DEFERRED_UPDATES_REPORT" 2>&1

That will fix the problem temporarly.

frzadmin at 2007-7-6 13:33:01 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 8
Hmm, the thing that most concerns me is that a bug that obvious should have been found in even the most cursory testing.
robertcohen at 2007-7-6 13:33:01 > top of Java-index,Administration Tools,Sun Update Connection-System...