[pca] 120011, 122660 Patch weirdness

[Rajiv Gunja]

Kevin,
The problem with that again is that it takes care of 122660 patches and does
not really take care of its prerequisites. Here is the reason why I have a
problem:

<root at agni03> pca -y -l 122660
Using /apps/incoming/pca/patchdiag.xref from May/30/08
Host: agni03 (SunOS 5.10/Generic_118833-23/sparc/sun4u)
List: 122660

Patch  IR   CR RSB Age Synopsis
------ -- - -- --- ---
-------------------------------------------------------
119578 29 < 30 R-- 637 SunOS 5.10: FMA Patch
118833 23 < 36 RS- 535 SunOS 5.10: kernel patch
118918 19 < 24 RS- 528 SunOS 5.10: Solaris Crypto Framework patch
119254 27 < 53 RS-  97 SunOS 5.10: Install and Patch Utilities Patch
126538 -- < 01 R-- 311 SunOS 5.10: i.manifest and r.manifest patch
120272 05 < 18 RS- 147 SunOS 5.10: SMA patch
122640 -- < 05 R-- 724 SunOS 5.10: zfs genesis patch
126897 -- < 02 R-- 311 SunOS 5.10: Fault Manager Patch
127755 -- < 01 R--  84 SunOS 5.10: Fault Manager patch
125503 -- < 02 R-- 311 SunOS 5.10: package-move-of-IP-objects patch
125547 -- < 02 R-- 311 SunOS 5.10: zoneadm indirect dependency patch
126419 -- < 01 R-- 311 SunOS 5.10: umountall patch
120011 -- < 14 RS- 309 SunOS 5.10: kernel patch
122660 -- < 10 --- 352 Obsoleted by: 120011-14 SunOS 5.10: zones patch

If you notice the last patch in the pca list is 122660, but there are other
patches required by 122660 which does not get installed because 125547
depends on 122660 and so 120011 fails.

After almost 4 hours of writing and testing, I have a script which will
download the patches and create a patch_order file which can be used to
install the patches in order. Once these patches are installed, we can
proceed as normal with installing other patches using pca.

I will attach my script and hope that this forum accepts text attachments.

If it does not attach it, please let me know and I will paste it in my
message text.

Hope this helps. Thanks

-GGR

---
Rajiv G Gunja

2008/7/17 Bliss, Kevin L <Bliss.Kevin at con-way.com>:

>  You could do it with a script by having the script install patch
> 122660-10, the script creates or copies an init script, the script reboots
> the server.  The init script that is created or copied, runs pca, deletes
> itself, and reboots (logging everything to a file).
>
>
>
>  ------------------------------
> *From:* pca-bounces at lists.univie.ac.at [mailto:
> pca-bounces at lists.univie.ac.at] *On Behalf Of *Rajiv Gunja
> *Sent:* Thursday, July 17, 2008 10:12 AM
> *To:* PCA (Patch Check Advanced) Discussion
> *Subject:* Re: [pca] 120011, 122660 Patch weirdness
>
>  Yes, I am doing that manually on my test servers, but I have about 200+
> servers in prod, and getting Engineers to follow this would be a pain, when
> they are working in the middle of the night.
>
> Was hoping if someone had automated it, by writing wrappers around the PCA.
>
>
> I currently have wrappers to automate and tailor it our Organisation's
> needs, but this conundrum is quite difficult/tedious to handle within
> scripts.
>
> -GGR
>
> ---
> Rajiv G Gunja
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.univie.ac.at/mailman/private/pca/attachments/20080717/cb361409/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 120011_fix.sh
Type: application/x-sh
Size: 5272 bytes
Desc: not available
Url : https://lists.univie.ac.at/mailman/private/pca/attachments/20080717/cb361409/attachment-0001.sh