Classification: UNCLASSIFIED
Caveats: NONE

I've been working on this for a bit and seem to be hitting some challenges.
To start: we have been using PCA for years here pretty much problem free.
We have a large number of Sol10 systems, many with zones, all patching happily.

I've now built five Solaris 11 systems on five T5-1B blades.
Four blades are each hosting 1 Solaris 10 branded zone.  
One blade is hosting 2 Branded zones.

When I started to patch the branded zones I ran our usual pca -yi missingrs 
and got zero patches!
Yes, there were R|S patches in the patchdiag.xref file to install.  
pca -yi missing will get me patches.

I think that the problem is related to the difference in uname output.
Or perhaps it’s a difference that also shows up in how the kernels are named.
But perl debugging is a weak point for me.  In the 20 years since I first met
perl I just never got strong in it.

Has anyone else run into this kind of problem before?

Here are some uname outputs.

uname -a result on Solaris 10 system:
SunOS hostnameA 5.10 Generic_150400-18 sun4v sparc sun4v

uname -a result on a Solaris 10 zone hosted on a Solaris 10 system:
SunOS hostnameZ1 5.10 Generic_150400-18 sun4v sparc sun4v

uname -a result on Solaris 10 Branded zone:
SunOS hostnameBZ1 5.10 Generic_Virtual sun4v sparc sun4v

BTW: under the heading of "when it rains it pours"...

In the midst of this work the Solaris 10 system that is used as our pca proxy 
has gone fubar'd and access to its replacement hardware (a hand-me-down) has 
been
delayed until Feb.  So in addition to trying to troubleshoot the missing vs 
missingrs 
issue I am also trying to move our PCA proxy over to the Solaris 11 patch repo 
system.

The good news about all of this...
I am having success using the pca option of fromfiles.  So if you are moving 
from 
Sol10 to Sol11 and can only have a *VERY* limited number of systems with 
external access
this is an option.  Our patching team is not thrilled by the extra steps.

Thank you,
michael



Classification: UNCLASSIFIED
Caveats: NONE


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to