[pca] Wrong patches downloaded

Rajiv Gunja opn.src.rocks at gmail.com
Sat Dec 13 18:48:32 CET 2008


Ron / Mike,
This is the same issue with Veritas MP3 patches. So what I do is to avoid
getting those listed in my "-l" listing and install these conflicting
patches separately and manually.

The team I work with supports 3000+ servers and having patches fail on them
is not fun as I need to explain or document. So I just create different
patch clusters which is installed on need basis.

I have added this line in my pca.conf, on the server which is being patched.

pattern=!VERITAS|Veritas|VXVM|VxVM|VRTS|vrts

-GGR

--
Rajiv G Gunja
Blog: http://ossrocks.blogspot.com


2008/12/12 Myers, Mike <Mike.Myers at nwdc.net>

> You have to prove it's...perfect?  Wow...
>
> PCA uses the patchdiag.xref file which has 10 fields (see
> http://sunsolve.sun.com/search/document.do?assetkey=1-9-240587-1 for the
> official documentation of it).
>
> Field 8 is "OS Version".  For this specific patch it's listed as
> "unbundled" which means this is a patch for a product that's not tied to an
> OS release.  But of course that's contradicted by the description...
>
> 110936|22|Apr/07/05| |S| |  |Unbundled|sparc;|...|Sun Management Center
> 3.0: (GA) Patch for Solaris 2.6
>
> So you can see Sun doesn't even aim for "perfect"
>
> Cheers,
>  - Mike.Myers <at> nwdc.net
> -----Original Message-----
> From: pca-bounces at lists.univie.ac.at [mailto:
> pca-bounces at lists.univie.ac.at] On Behalf Of Ron Halstead
> Sent: Friday, December 12, 2008 1:45 PM
> To: PCA (Patch Check Advanced) Discussion
> Subject: [pca] Wrong patches downloaded
>
> Using the following pca options, I ran my pca wrapper script on a
> Solaris 8 machine.
> The following patches were downloaded from my patch proxy server.
>
> pca --nocheckxref \
>    --patchdir=${TMPDIR} \
>    --xrefdir=/patches/pca/htdocs/${ROLE} \
>    --patchurl=http://${SERVER}/dev/pca-proxy.cgi \
>    --xrefurl=http://${SERVER}/dev/pca-proxy.cgi \
>    --fromfiles=/tmp/${HOSTNAME}_ \
>    --install $PATCHGRP | tee
> /patches/pca/logs/${HOSTNAME}.patchlog.`date +%y%m%d` 2>&1
>
> 110936 -- < 22 -S- 999 Sun Management Center 3.0: (GA) Patch for Solaris
> 2.6
> 110937 -- < 22 -S- 999 Sun Management Center 3.0: (GA) Patch for Solaris 7
> 110971 -- < 22 -S- 999 Sun Management Center 3.0: (RR) Patch for Solaris
> 2.6
> 110972 -- < 22 -S- 999 Sun Management Center 3.0: (RR) Patch for Solaris 7
>
> As you can see, they are for Solaris 2.6 and 7. not Solaris 8. How did
> this happen? In order to use my
> pca wrapper scripts in production, I must prove to management that pca
> is "perfect". I believe I can
> convince my boss that this is so, but I would like to know the cause.
>
> By the way, the rest of the patches were correctly installed and I did
> not have this problem on a
> Solaris 10 machine.
>
> Ron
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.univie.ac.at/mailman/private/pca/attachments/20081213/c3d2dc56/attachment.html 


More information about the pca mailing list