headers
ASkinner | 18 Jun 2013 17:23

Bad patches - S10_u11 update

Hey all;

Am tracing two bad patches in the S10_u11 patch flood. While there's not that much of an impact (only impacted 8 machines for me out of thousands), I thought I'd share this with all.

I background PCA and log all 'patch transactions'. (Oracle has all my PCA logs)

Anyway, the 8 machines in question are running iscsi LUNs which are all imported as zpools / datasets / for zones.

The case was a Sev-1 but is now a Sev-3 awaiting a "senior driver engineer".

Bad patches:
122911-31 <- Not so sure I trust the engineer that this is bad (makes no sense to me)
124630-70

If iscsi fails for you, manually start using scripts under /lib/svc/method

Cheers,

Andrew.

CONFIDENTIALITY WARNING 
This communication, including any attachments, is for the exclusive use of addressee and may contain
proprietary and/or confidential information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you are not the intended
recipient, please notify the sender immediately by return e-mail, delete this communication and
destroy all copies.

AVERTISSEMENT RELATIF À LA CONFIDENTIALITÉ 
Ce message, ainsi que les pièces qui y sont jointes, est destiné à l’usage exclusif de la personne à
laquelle il s’adresse et peut contenir de l’information personnelle ou confidentielle. Si le
lecteur de ce message n’en est pas le destinataire, nous l’avisons par la présente que toute
diffusion, distribution, reproduction ou utilisation de son contenu est strictement interdite.
Veuillez avertir sur-le-champ l’expéditeur par retour de courrier électronique et supprimez ce
message ainsi que toutes les pièces jointes.
Permalink | Reply | 0 comments |
headers
Harvey, Dominic | 18 Jun 2013 01:54

Patch xxxxxx-xx is for global zone only - cannot be installed on non-global zone.

Why pca try to install patch for global zone, in local zone?

 

 

#grep "global zone only" Patches_installation_2013Q2.log                              

Patch 119764-08 is for global zone only - cannot be installed on non-global zone.

Patch 121430-86 is for global zone only - cannot be installed on non-global zone.

Patch 142373-03 is for global zone only - cannot be installed on non-global zone.

Patch 140912-02 is for global zone only - cannot be installed on non-global zone.

Patch 142088-03 is for global zone only - cannot be installed on non-global zone.

Patch 142543-02 is for global zone only - cannot be installed on non-global zone.

Patch 142933-05 is for global zone only - cannot be installed on non-global zone.

Patch 143643-08 is for global zone only - cannot be installed on non-global zone.

Patch 144742-02 is for global zone only - cannot be installed on non-global zone.

Patch 146694-02 is for global zone only - cannot be installed on non-global zone.

Patch 147442-01 is for global zone only - cannot be installed on non-global zone.

Patch 147147-26 is for global zone only - cannot be installed on non-global zone.

Patch 147143-17 is for global zone only - cannot be installed on non-global zone.

Patch 147793-07 is for global zone only - cannot be installed on non-global zone.

Patch 148023-03 is for global zone only - cannot be installed on non-global zone.

Patch 148027-04 is for global zone only - cannot be installed on non-global zone.

Patch 148029-01 is for global zone only - cannot be installed on non-global zone.

Patch 148035-06 is for global zone only - cannot be installed on non-global zone.

Patch 148043-02 is for global zone only - cannot be installed on non-global zone.

Patch 148071-10 is for global zone only - cannot be installed on non-global zone.

Patch 148112-02 is for global zone only - cannot be installed on non-global zone.

Patch 148223-02 is for global zone only - cannot be installed on non-global zone.

Patch 148237-01 is for global zone only - cannot be installed on non-global zone.

Patch 148309-03 is for global zone only - cannot be installed on non-global zone.

Patch 148322-07 is for global zone only - cannot be installed on non-global zone.

Patch 148328-03 is for global zone only - cannot be installed on non-global zone.

Patch 148336-01 is for global zone only - cannot be installed on non-global zone.

Patch 148342-06 is for global zone only - cannot be installed on non-global zone.

Patch 148381-02 is for global zone only - cannot be installed on non-global zone.

Patch 148383-01 is for global zone only - cannot be installed on non-global zone.

Patch 148415-02 is for global zone only - cannot be installed on non-global zone.

Patch 148419-03 is for global zone only - cannot be installed on non-global zone.

Patch 148423-01 is for global zone only - cannot be installed on non-global zone.

Patch 148559-07 is for global zone only - cannot be installed on non-global zone.

Patch 148565-01 is for global zone only - cannot be installed on non-global zone.

Patch 148571-01 is for global zone only - cannot be installed on non-global zone.

Patch 148768-01 is for global zone only - cannot be installed on non-global zone.

Patch 148881-01 is for global zone only - cannot be installed on non-global zone.

Patch 148888-03 is for global zone only - cannot be installed on non-global zone.

Patch 148975-01 is for global zone only - cannot be installed on non-global zone.

Patch 148985-01 is for global zone only - cannot be installed on non-global zone.

Patch 149057-01 is for global zone only - cannot be installed on non-global zone.

Patch 149163-01 is for global zone only - cannot be installed on non-global zone.

Patch 149165-01 is for global zone only - cannot be installed on non-global zone.

Patch 149173-03 is for global zone only - cannot be installed on non-global zone.

Patch 149175-02 is for global zone only - cannot be installed on non-global zone.

Patch 149277-01 is for global zone only - cannot be installed on non-global zone.

Patch 149622-01 is for global zone only - cannot be installed on non-global zone.

Patch 149895-01 is for global zone only - cannot be installed on non-global zone.

Patch 150117-01 is for global zone only - cannot be installed on non-global zone.

Patch 150123-01 is for global zone only - cannot be installed on non-global zone.

Patch 150125-01 is for global zone only - cannot be installed on non-global zone.

Patch 150157-01 is for global zone only - cannot be installed on non-global zone.

 

# /opt/cgi/scripts/pca --version

pca 20130502-01

 

# /opt/cgi/scripts/pca  -y -l  missingrs

Using /var/tmp/patchdiag.xref from Apr/30/13

Host: xxxxyyyyy (SunOS 5.10/Generic_148888-03/sparc/sun4v)

List: missingrs (55/6377)

 

Patch  IR   CR RSB Age Synopsis

------ -- - -- --- --- -------------------------------------------------------

119764 07 < 08 RS- 203 SunOS 5.10 : ipmitool patch

121430 83 < 86 RS-  98 SunOS 5.8 5.9 5.10: Live Upgrade Patch

142373 02 < 03 R--  67 SunOS 5.10: AST Graphics Patch

125719 47 < 49 RS-  67 X11 6.8.0: Xorg server patch

140912 01 < 02 R-- 116 SunOS 5.10: ufsrestore patch

142088 02 < 03 R--  87 SunOS 5.10: fp.so patch

142543 01 < 02 R--  49 SunOS 5.10: svc-snmpdx libssagent.so.1 mibiisa snmpdx snmpdx.xm pa

142933 04 < 05 R-- 131 SunOS 5.10: failsafe patch

143643 06 < 08 R-- 199 SunOS 5.10: libMPAPI.so libmpscsi_vhci.so libMPAPI.so.1 libmpscsi_

144742 -- < 02 R-- 221 SunOS 5.10: JPool.jar patch

146694 -- < 02 RS- 131 SunOS 5.10: cron patch

147442 -- < 01 R-- 131 SunOS 5.10: place holder patch

147147 -- < 26 RS- 131 SunOS 5.10: kernel patch

147143 -- < 17 RS- 119 SunOS 5.10: iSCSI patch

147793 -- < 07 RS-  90 SunOS 5.10: kerberos patch

148023 -- < 03 R-- 131 SunOS 5.10: bmc patch

148027 -- < 04 RS-  52 SunOS 5.10: compress cp cpio ln mv pack pax tar patch

148029 -- < 01 R-- 131 SunOS 5.10: ntp patch

148035 -- < 06 R-- 130 SunOS 5.10: igb patch

148043 -- < 02 R-- 131 SunOS 5.10: routed patch

148071 -- < 10 RS-  90 SunOS 5.10: openssl patch

148112 -- < 02 RS- 131 SunOS 5.10: root_archive patch

148223 -- < 02 R-- 131 SunOS 5.10: zonecfg patch

148237 -- < 01 R-- 131 SunOS 5.10: vold patch

148309 -- < 03 RS- 131 SunOS 5.10: dhcp patch

148322 -- < 07 R-- 105 SunOS 5.10: ixgbe patch

148328 -- < 03 R-- 102 SunOS 5.10: dladm patch

148336 -- < 01 R-- 131 SunOS 5.10: awk patch

148338 -- < 04 R--  52 SunOS 5.10: s9_brand patch

148342 -- < 06 R-- 131 SunOS 5.10: nxge patch

148381 -- < 02 R-- 131 SunOS 5.10: cdrw patch

148383 -- < 01 RS- 131 SunOS 5.10: IPv6 patch

148415 -- < 02 R--  98 SunOS 5.10: rdsv3 ibcm patch

148419 -- < 03 R--  91 SunOS 5.10: nss_dns patch

148423 -- < 01 RS- 131 SunOS 5.10: /usr/ccs/bin/error patch

148559 -- < 07 R--  52 SunOS 5.10: timezone patch

148565 -- < 01 RS- 131 SunOS 5.10: fdformat patch

148571 -- < 01 R-- 131 SunOS 5.10: fcinfo patch

148768 -- < 01 RS- 131 SunOS 5.10: calendar diff3 spell uupick patch

148881 -- < 01 RS- 131 SunOS 5.10: xntpd patch

148888 -- < 03 RS-  55 SunOS 5.10: kernel patch

148975 -- < 01 RS- 131 SunOS 5.10: in.rexecd patch

148985 -- < 01 RS- 131 SunOS 5.10: libgss patch

149057 -- < 01 R-- 131 SunOS 5.10: llc2 patch

149163 -- < 01 RS- 131 SunOS 5.10: rlmod patch

149165 -- < 01 RS- 131 SunOS 5.10: timod patch

149173 -- < 03 R-- 131 SunOS 5.10: emlxs driver patch

149175 -- < 02 R-- 131 SunOS 5.10: qlc patch

149277 -- < 01 R-- 131 SunOS 5.10: stmsboot patch

149622 -- < 01 R-- 131 SunOS 5.10: oce patch

149895 -- < 01 RS-  67 SunVTS 7.0 Patch Set 16 consolidation patch

150117 -- < 01 RS-  87 SunOS 5.10: mac patch

150123 -- < 01 RS-  90 SunOS 5.10: sharefs patch

150125 -- < 01 R-- 104 SunOS 5.10: ZFS patch

150157 -- < 01 RS-  87 SunOS 5.10: RPC patch

 

# zoneadm list -cv

  ID NAME             STATUS     PATH                           BRAND    IP

   1 xxxxyyyy         running    /                              native   shared

 

 

Merci et bonne journée

Thank you and have a good day

 

 

 

Attachment (Dominic Harvey.vcf): text/x-vcard, 1728 bytes
Permalink | Reply | 4 comments |
headers
Thomas Bleek | 12 Jun 2013 12:01
Picon
Favicon

new Solaris 10 "patching strategy" at oracle???

Hello,

I wonder, if this is a sign of a change in oracle patching? It seems, that the last vulnerability of sudo is
"patched" by installing an new package. With pca I don't see a "normal" patch for this:-(

Could someone explain this, perhaps Don?

Thanks,
thomas
--
Dr. Thomas Bleek, Netzwerkadministrator
Helmholtz-Zentrum Potsdam
Deutsches GeoForschungsZentrum
Telegrafenberg A20/225
D-14473 Potsdam
Tel.: +49 331 288- 1818/1681 Fax.: 1730 Mobil: +49 172 1543233
E-Mail: bl <at> gfz-potsdam.de
Attachment (smime.p7s): application/pkcs7-signature, 4685 bytes
Permalink | Reply | 4 comments |
headers
Martin Paul | 2 May 2013 11:22
Picon
Picon
Favicon

New release: 20130502-01

A new release of PCA has just been published. Here's a list of new 
features and changes:

  * Do not pass on Recommended flag with --minimal option
  * Correct patch obsoletions from installed patches with --minimal option
  * Fix rare bug of certain patches not showing up with --minimal option
  * Remove link to patch README on wesunsolve.net in HTML output
  * Temporary workaround for problem with Oracle server and wget from 
OpenCSW
  * Whitelist: add 147143, 147144
  * Whitelist: add 147147, 148148, 148027, 148028
  * Whitelist: add 149173, 149174, 149175, 149176
  * Apply check: add 147416, 147419

Update:
   pca --update now

Download:
   http://www.par.univie.ac.at/solaris/pca/installation.html

MD5: 70c76b041938d4d57ba7f529a783011b
Permalink | Reply | 0 comments |
headers
Glen Gunselman | 25 Apr 2013 23:36
Favicon

PCA selects SPARC patch on X86

After installing the Solaris 10 CPU_2013-04 on an X4500 I ran pca –list missingrs.  Patch 147416-02 was listed as missing but the x86 version is 147419-02 is installed.

 

I do not recall seeing this in the past but I do not patch this server often.

 

I found the following details:

 

grep 14741 /var/tmp/patchdiag.xref

147416|02|Dec/03/12| |S| |  |Unbundled|all;sparc;|SUNWsefms:6.9.0,REV=2011.11.13.21.31.38;SUNWstkraidsa:6.9.0,REV=2011.11.13.21.31.44;SUNWse6130ui:6.9.0,REV=2011.11.13.21.32.51;SUNWsesscs:6.9.0,REV=2011.11.13.21.32.51;SUNWstkcamcd:6.9.0,REV=2011.11.13.21.32.51;140064-01;140064-02;140064-03;|SunOS 5.9 5.10 CAM 6.9.0 bug fixes.

147417|02|Dec/03/12| |S| |  |Unbundled|||Windows CAM 6.9.0 bug fixes.

147418|02|Dec/04/12| |S| |  |Unbundled|||Linux RHEL SuSE CAM 6.9.0 bug fixes.

147419|02|Dec/03/12| |S| |  |Unbundled|all;i386;|SUNWsefms:6.9.0,REV=2011.11.13.21.31.38;SUNWstkraidsa:6.9.0,REV=2011.11.13.21.31.44;SUNWse6130ui:6.9.0,REV=2011.11.13.21.32.51;SUNWsesscs:6.9.0,REV=2011.11.13.21.42.41;SUNWstkcamcd:6.9.0,REV=2011.11.13.21.32.51;140064-01;140064-02;140064-03;|SunOS 5.10_x86 CAM 6.9.0 bug fixes.

 

/var/tmp/pca --list 147416 147419 --root="/.alt.s10u10CPU_2013-04" --patchdir="/var/tmp/pcatmp"

Using /var/tmp/patchdiag.xref from Apr/24/13

Host: beaker (SunOS 5.10/Generic_147441-19/i386/i86pc)

Root: /.alt.s10u10CPU_2013-04

List: 147416 147419 (2/286)

 

Patch  IR   CR RSB Age Synopsis

------ -- - -- --- --- -------------------------------------------------------

147416 -- < 02 -S- 143 SunOS 5.9 5.10 CAM 6.9.0 bug fixes.

147419 02 = 02 -S- 143 SunOS 5.10_x86 CAM 6.9.0 bug fixes.

 

/var/tmp/pca --list missingrs --root="/.alt.s10u10CPU_2013-04" --patchdir="/var/tmp/pcatmp" | grep 14741

147416 -- < 02 -S- 143 SunOS 5.9 5.10 CAM 6.9.0 bug fixes.

 

/var/tmp/pca --version

pca 20120829-01

 

 

 

 

Glen Gunselman

Systems Software Specialist

Information Technology

Emporia State University

1200 Commerical St

Emporia Kansas 66801

 

Permalink | Reply | 2 comments |
headers
Laurent Blume | 25 Apr 2013 09:47
Favicon

Oracle webserver has an SSL bug -> incompatible with OpenSSL 1.0

Hello all,

An heads up:

If you have installed OpenCSW's wget, you might have noticed that for a 
few days, PCA is not working anymore, it cannot download the 
patchdiag.xref file.

This has been analyzed as an issue on the Oracle server side, which 
makes it incompatible with OpenSSL 1.0:

http://lists.opencsw.org/pipermail/users/2013-April/009568.html

https://www.opencsw.org/mantis/view.php?id=5068

A ticket has been open with Oracle, but well, if somebody here has 
faster access to get it fixed, that'd be nice.

Martin, there is a workaround in the first link that you might consider 
to include in PCA when using OpenCSW's wget.

Laurent
Permalink | Reply | 1 comment |
headers
Drew Skinner | 19 Apr 2013 17:33
Picon

Query regarding patches currently running

Hi;

While I haven't run into the problem with SUNWastfb - I am encountering another issue that I haven't seen before.

First, I think I remember seeing that PCA can patch OBP/POST ~ ILOM/ALOM/ELOM. Not sure if that's right (remember I think I saw) <g>

Anyway, I'm using patchdiag.xref from Mar/18/13.

For the systems I have that are listing themselves as downrev (OBP/POST ~ ILOM/ALOM/ELOM) I'm finding that the ILOM's are freezing during the patching process.

Since I background PCA and reboot later, it might be a few days before ILOM service is restored. The only other thought I have is that a full power off / on may be required to restore them. Any ideas here (I haven't seen this behaviour before).

Also, I'm seeing with the S10_u11 update that you can't fully update a system with running zones. There are workarounds I can use, but I'm curious if the above could be related.

Thanks,


Drew.
Permalink | Reply | 2 comments |
headers
Frank Langelage | 12 Apr 2013 20:38
Picon

"Bad patch installed" and "does not match"

Two questions regarding pca output and patches as of today.

pca in verbose mode says today:
------------
osname from uname: SunOS
Reading from /usr/bin/showrev -p  2>/dev/null
patchdiag.xref size: 2303118
Using /var/tmp/patchdiag.xref from Apr/11/13
*Bad patch installed: 144560-04*
SUNWswmt patches: 108987 108988 110763 112951 114194 119254 119255
120201-04 required by 125719: already installed
*142373-03 required by 125719*
*142373-03 required by 125719: does not match*
144500-19 required by 125719: already installed
Host: sb2000 (SunOS 5.10/Generic_148888-02/sparc/sun4u)
List: missing (1/1)

Patch  IR   CR RSB Age Synopsis
------ -- - -- --- --- 
-------------------------------------------------------
125719 48 < 49 RS-   1 X11 6.8.0: Xorg server patch

Looking for 125719-49 (1/1)
Found patch file
------------------------------------------------------------------------------
Download Summary: 1 total, 0 successful, 1 skipped, 0 failed

Trying to get rid of the "Bad patch" I get

root <at> sb2000:/  patchrm 144560-04

...

The following requested patches will not be removed because
they have been made obsolete by other patches already
installed on the system

            0 Patch 144560-04 is obsoleted by 147147-26, which has 
already been installed on the system. It should be removed first.

Is it correct, that 144560-04 is listed as bad patch?
How should I deal with this situation? Remove 147147-26 then 144560-04 
and then reapply 147147-26 again?

root <at> sb2000:/home/langfr/Patches ksh pca -in
Using /var/tmp/patchdiag.xref from Apr/11/13
Host: sb2000 (SunOS 5.10/Generic_148888-02/sparc/sun4u)
List: missing (1/1)

Patch  IR   CR RSB Age Synopsis
------ -- - -- --- --- 
-------------------------------------------------------
125719 48 < 49 RS-   1 X11 6.8.0: Xorg server patch

Looking for 125719-49 (1/1)
Found patch file

Installing 125719-49 (1/1)
Unzipping patch
Running patchadd

....

The following requested patches will not be installed because
at least one required patch is not installed on this system.

            0 For patch 125719-49, required patch 142373-03 does not exist.

The missing patch is in patchdiag.ref
142373|03|Apr/11/13| | | | 
|10|sparc;|SUNWastfb:10.0.0,REV=2009.02.20;SUNWastfbcf:10.0.0,REV=2009.02.26;|SunOS 
5.10: AST Graphics Patch

What does "does not match" mean?
Permalink | Reply | 2 comments |
headers
Brookins, Neil (Philadelphia | 4 Mar 2013 15:57
Favicon

patch 118666-42 fails on sparse root zones

When I patch my global zone with 118666-42, it installs OK in the global zone, then it installs OK when it does the whole root zones.

But, when there are sparse root zones, where the /usr partition is inherited from the global zone, it fails due to read-only file system.

The good news is that despite the failure, and the subsequent back-out of the partial patch, when I run “java -version” it stills sees the “new” version because its inheriting the patched version from the global zone.

 

My concern here is that errors show up in the PCA install log (for the failed patch) and the reports that show missing patches (pca -l) make it look like there is a missing patch. Auditors don’t like this. Clearly, the patch isn’t truly missing if the patched version is installed and runnable as shown below.

 

This looks like a bug in the patch itself causing it to not handle sparse zones in a user friendly way. Note that the three other Java patches do not have this issue.  I don’t think there is a problem with PCA itself; its simply reporting the errors that patchadd is reporting back.

 

$ /usr/jdk/jdk1.5.0_40/bin/java -version

java version "1.5.0_40"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_40-b02)

Java HotSpot(TM) Server VM (build 1.5.0_40-b02, mixed mode)

 

$ ../pca -l --minimal missingr

Using /var/tmp/patchdiag.xref from Mar/03/13

Host: V210_sparse_zone (SunOS 5.10/Generic_147147-26/sparc/sun4u)

List: missingr-minimal (1/14)

 

Patch  IR   CR RSB Age Synopsis

------ -- - -- --- --- -------------------------------------------------------

118666 38 < 42 RS-  14 JavaSE 5.0: update 40 patch (equivalent to JDK 5.0u40)

 

$ more /var/tmp/118666-42.log.11833

…

rm: /a/usr/jdk/jdk1.5.0_40 not removed: Read-only file system

rm: /a/usr/jdk/jdk1.5.0_40 not removed: Read-only file system

ln: cannot create /a/usr/jdk/jdk1.5.0_40/jdk1.5.0: Read-only file system

ln: cannot create /a/usr/java/jdk1.5.0_40: Read-only file system

ln: cannot create /a/usr/bin/javaws: Read-only file system

/a/var/sadm/pkg/SUNWj5rt/install/postinstall: /a/usr/share/control-center-2.0/ca

pplets/sun_java.desktop: cannot create

chmod: WARNING: can't change /a/usr/share/control-center-2.0/capplets/sun_java.d

esktop

chown: /a/usr/share/control-center-2.0/capplets/sun_java.desktop: Read-only file

system

chgrp: /a/usr/share/control-center-2.0/capplets/sun_java.desktop: Read-only file

system

cp: cannot create /a/usr/share/pixmaps/sun-java.png: Read-only file system

cp: cannot create /a/usr/share/icons/HighContrast/48x48/apps/sun-java.png: Read-

only file system

cp: cannot create /a/usr/share/icons/HighContrastInverse/48x48/apps/sun-java.png

: Read-only file system

cp: cannot create /a/usr/share/icons/LowContrast/48x48/apps/sun-java.png: Read-o

nly file system

/a/var/sadm/pkg/SUNWj5rt/install/postinstall: /a/usr/share/gnome/mime-info/java-

archive.keys: cannot create

pkgadd: ERROR: postinstall script did not complete successfully

 

Installation of <SUNWj5rt> failed.

 

Neil G. Brookins
Identity and Authentication Solutions - IT Global Solutions

Towers Watson

1500 Market Street | Philadelphia, PA 19102

Phone: +1 215 246 6046

neil.brookins <at> towerswatson.com

 

Notice of Confidentiality
This transmission contains information that may be confidential. It has been prepared for the sole and exclusive use of the intended recipient and on the basis agreed with that person. If you are not the intended recipient of the message (or authorized to receive it for the intended recipient), you should notify us immediately; you should delete it from your system and may not disclose its contents to anyone else.


This e-mail has come to you from Towers Watson Delaware Inc.
Permalink | Reply | 1 comment |
headers
Brookins, Neil (Philadelphia | 1 Mar 2013 18:41
Favicon

pca recommends non-recommended patch

I have a newly installed Solaris 10 U11 host.  I patched it a couple days ago with “pca --minimal missingr”

Today, when I run “pca -l --minimal missingr“ using the new xref it says:

 

Using /var/tmp/patchdiag.xref from Feb/28/13

Host: T2000_hostname (SunOS 5.10/Generic_147147-26/sparc/sun4v)

List: missingr-minimal (1/1)

 

Patch  IR   CR RSB Age Synopsis

------ -- - -- --- --- -------------------------------------------------------

148338 -- < 03 R--   1 SunOS 5.10: s9_brand patch

 

The host has 148161-02 installed because it’s in the U11 release.

 

Here is the trace of the patch obsolescence in order,

starting from the current recommended through the newest:

139944-01 has the “R” flag.             It was obsoleted by 148161-02

148161-02 does NOT have “R” flag. It was obsoleted by 148338-03.

148338-03 does NOT have “R” flag.

 

Based on my understanding, PCA’s recommendation to install 148338-03 is not correct when using the --minimal flag.

It should have seen that the currently installed version, 148161-02, was already newer than the recommended, 139944-01 version, therefore no newer patch is needed.

 

This behavior occurs in all recent versions of PCA, both development and stable.

 

Neil G. Brookins
Identity and Authentication Solutions - IT Global Solutions

Towers Watson

1500 Market Street | Philadelphia, PA 19102

Phone: +1 215 246 6046

neil.brookins <at> towerswatson.com

 

Notice of Confidentiality
This transmission contains information that may be confidential. It has been prepared for the sole and exclusive use of the intended recipient and on the basis agreed with that person. If you are not the intended recipient of the message (or authorized to receive it for the intended recipient), you should notify us immediately; you should delete it from your system and may not disclose its contents to anyone else.


This e-mail has come to you from Towers Watson Delaware Inc.
Permalink | Reply | 2 comments |
headers
Brookins, Neil (Philadelphia | 27 Feb 2013 18:58
Favicon

patch install fail

I just built a new T2000 using Solaris10 U11.

I then patched it with “pca --install --minimal missingr”

The following six patches failed to install:

 

# ./pca -l --minimal missingr

Using /var/tmp/patches/./patchdiag.xref from Feb/26/13

Host: xxxxxx (SunOS 5.10/Generic_147147-26/sparc/sun4v)

List: missingr-minimal (6/3818)

 

Patch  IR   CR RSB Age Synopsis

------ -- - -- --- --- -------------------------------------------------------

138876 -- < 01 RS- 999 Obsoleted by: 138876-02 SunOS 5.10: usr/lib/inet/in.dhcpd patch

145929 -- < 05 R-- 573 Obsoleted by: 145929-06 SunOS 5.10: igb driver Patch

145953 -- < 06 R-- 573 Obsoleted by: 145953-07 SunOS 5.10: emlxs driver Patch

146232 -- < 21 RS- 149 Obsoleted by: 146232-22 SunOS 5.10: iSCSI patch

146954 -- < 03 R-- 573 Obsoleted by: 146954-04 SunOS 5.10: routed patch

148169 -- < 03 R-- 376 Obsoleted by: 148169-04 SunOS 5.10: ixgbe patch

 

I picked “emlxs driver Patch“ to trace the trail of “Obsoleted by…:” to confirm that a newer patch was already installed.

The xref file shows 145953-06 is Obsoleted by: 145953-07

The xref file shows 145953-07 is Obsoleted by: 149173-03

The “showrev -p” shows that Patch: 149173-03 is installed.

Therefore, 145953-06 is not needed.

 

Next I look at “igb driver Patch” to trace the trail…

The xref shows 145929-05 is Obsoleted by: 145929-06

The xref does not have 145929-06 listed.

But the xref does list 145929-09 so we know -06 is obsoleted by -09 which in turn is Obsoleted by: 148035-06

The “showrev -p” shows that Patch: 148035-06 is installed.

Therefore, 145929-05 is not needed.

 

In the above 2 cases, we can easily trace the trail using only the xref file. I assume that the other 4 cases are similar.

We do not have to download any additional data to derive the path of obsolescence.

I’d like to automate this process in such a way that the tool would automatically know that these patches are not needed to be installed and avoid having the failures. The goal would be that patches are not attempted to be installed if they are already obsoleted by any newer patch. Would this new functionality be something that PCA could be enhanced to perform?

 

Neil G. Brookins
Identity and Authentication Solutions - IT Global Solutions

Towers Watson

1500 Market Street | Philadelphia, PA 19102

Phone: +1 215 246 6046

neil.brookins <at> towerswatson.com

 

Notice of Confidentiality
This transmission contains information that may be confidential. It has been prepared for the sole and exclusive use of the intended recipient and on the basis agreed with that person. If you are not the intended recipient of the message (or authorized to receive it for the intended recipient), you should notify us immediately; you should delete it from your system and may not disclose its contents to anyone else.


This e-mail has come to you from Towers Watson Delaware Inc.
Permalink | Reply | 2 comments |

Gmane