124615-01 for x86 marked as sparc - plus 124614-01 doesn't apply

Here's part of smpatch analyze on my sparc system:

124615-01 SunOS 5.10_x86: sconadm proxy: UnknownHostException

124614-01 SunOS 5.10: sconadm proxy: UnknownHostException

Looking at the patchinfo and readme for 124515-01:

root nebula-bne /var/sadm/spool > more 124615-01.jar.dir/124615-01/patchinfo

PATCHINFOVERSION="1.0"

PATCHID=124615-01

PATCH_CORRECTS='BaseOS.SolarisCore-5.10'

PATCH_ARCH='sparc'

PATCH_OS='SunOS'

PATCH_OSRELEASE='5.10'

PATCH_PROPERTIES='clientusr clientroot'

Patch-ID# 124615-01

...

Keywords: basic registration, solaris registration, sconadm,"unknown host"

Synopsis: SunOS 5.10_x86: sconadm proxy: UnknownHostException

Date: Nov/12/2006

Install Requirements: NA

Solaris Release: 10_x86

SunOS Release: 5.10_x86

Unbundled Product:

Unbundled Release:

Xref: This patch availablefor SPARC as patch 124614

Topic:

Relevant Architectures: i386

So we have yet another meta-data problem with a patch. This joins the three other inapplicable patches that updatemanager wants to apply to my system.

But when I run smpatch update both flavors of the patch fail mysteriously:

Failed to install patch 124615-01.

Utility used to install the update failed with exit code 8.

Checking installed patches...Patchadd is terminating.

Transition old-style patching.

Nov 17 16:07:14 nebula-bne root: => Thread[Thread-19,5,main] <=Problem installing patches: Received a Manipulable event.

Nov 17 16:07:14 nebula-bne root: => Thread[Thread-19,5,main] <=Problem installing patches: Received a Manipulable event.

Nov 17 16:07:15 nebula-bne root: => com.sun.patchpro.util.PatchBundleInstaller@15dd32a <=Failed to install patch 124615-01.

Nov 17 16:07:15 nebula-bne root: => com.sun.patchpro.util.PatchBundleInstaller@15dd32a <=Failed to install patch 124615-01.

Nov 17 16:07:15 nebula-bne root: [ID 702911 user.alert] => com.sun.patchpro.util.PatchBundleInstaller@15dd32a <=Failed to install patch 124615-01.

Nov 17 16:07:15 nebula-bne root: [ID 702911 user.alert] => com.sun.patchpro.util.PatchBundleInstaller@15dd32a <=Failed to install patch 124615-01.

Failed to install patch 124615-01.

Nov 17 16:07:15 nebula-bne root: => Thread[Thread-19,5,main] <=Problem installing patches: ALERT: Failed to install patch 124615-01.

Nov 17 16:07:15 nebula-bne root: => Thread[Thread-19,5,main] <=Problem installing patches: ALERT: Failed to install patch 124615-01.

ALERT: Failed to install patch 124615-01.

Failed to install patch 124614-01.

Utility used to install the update failed with exit code 8.

Checking installed patches...Patchadd is terminating.

Transition old-style patching.

Nov 17 16:07:18 nebula-bne root: => Thread[Thread-19,5,main] <=Problem installing patches: Received a Manipulable event.

Nov 17 16:07:18 nebula-bne root: => Thread[Thread-19,5,main] <=Problem installing patches: Received a Manipulable event.

Nov 17 16:07:18 nebula-bne root: => com.sun.patchpro.util.PatchBundleInstaller@15dd32a <=Failed to install patch 124614-01.

Nov 17 16:07:18 nebula-bne root: => com.sun.patchpro.util.PatchBundleInstaller@15dd32a <=Failed to install patch 124614-01.

Nov 17 16:07:18 nebula-bne root: [ID 702911 user.alert] => com.sun.patchpro.util.PatchBundleInstaller@15dd32a <=Failed to install patch 124614-01.

Nov 17 16:07:18 nebula-bne root: [ID 702911 user.alert] => com.sun.patchpro.util.PatchBundleInstaller@15dd32a <=Failed to install patch 124614-01.

Failed to install patch 124614-01.

Nov 17 16:07:18 nebula-bne root: => Thread[Thread-19,5,main] <=Problem installing patches: ALERT: Failed to install patch 124614-01.

Nov 17 16:07:18 nebula-bne root: => Thread[Thread-19,5,main] <=Problem installing patches: ALERT: Failed to install patch 124614-01.

ALERT: Failed to install patch 124614-01.

Now if I try to add the patch manually:

> smpatch add -i 124614-01

add patch 124614-01

Transition old-style patching.

it reports no errors but does nothing and the patch is not installed. Is there supposed to be a log file somewhere?

Finally switching to the patch directory and using patachadd directly I see the true problem:

The following requested patches have packages not installed on the system

Package SUNWscn-base from directory SUNWscn-base in patch 124614-01 is not installed on the system. Changesforpackage SUNWscn-base will not be applied to the system.

It's the scn-base package not installed problem again.

These meta-data glitches in the patches should be the highest priority to get fixed - it should take a couple of days to correct and redeploy them.

[5256 byte] By [davidholmes] at [2007-11-26 11:33:28]
# 1

Yes, this is another metadata problem and is logged as bug 6494650. The problem as you have found is that the architecture is incorrectly marked as sparc:

We agree these patch metadata issues cause a lot of grief and need to be fixed quickly. We are looking at ways of improving our processes so that this kind of issue can be resolved quickly when it arises, and also to prevent it happening in the first place.

ForumModerator at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2
Can you comment on "smpatch add" not reporting any errors?
davidholmes at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 3
At this time i'm not sure why it's failing silently. I have though been able to recreate the silent failure so i'll get someone to review and and provide an update.
ForumModerator at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 4
Would it be possible for you to provide us with the return code for 'patchadd 124614-01', this may shed some light as to why the patch is failing silently.You should find this in /var/sadm/patch/124614-01/log
ForumModerator at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 5
There is no log file.It is not patchadd that fails silently (it reports that the base package isn't installed) but "smpatch add".
davidholmes at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 6

The return code of the last command run is stored in $? variable.

As such please run the patchadd attempt again until it fails and then immediately afterwards run the following -

# echo $?

It should output a the return code number of the patchadd command (which we suspect may be 0, and as such would silently fail when running thru smpatch).

Please ignore the case ref below it's purely an internal ref number we're using whilst investigating this issue (in order to tarck our communication between the different groups looking into it)

Case ID: 11135591

ForumModerator at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 7

Sorry for the delay in responding. I misunderstood what you were asking for.

root nebula-bne /var/sadm/spool/124614-01.jar.dir > patchadd 124614-01/

Validating patches...

Loading patches installed on the system...

Done!

Loading patches requested to install.

Done!

The following requested patches have packages not installed on the system

Package SUNWscn-base from directory SUNWscn-base in patch 124614-01 is not installed on the system. Changes for package SUNWscn-base will not be applied to the system.

Checking patches that you specified for installation.

Done!

The following requested patches will not be installed because

the packages they patch are not installed on this system.

0 Packages from patch 124614-01 are not installed on the system.

root nebula-bne /var/sadm/spool/124614-01.jar.dir > echo $?

8

root nebula-bne /var/sadm/spool/124614-01.jar.dir >

davidholmes at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 8
Ta.-- Modski
ForumModerator at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 9
I too am having problems with 124614-01. The patch fails to apply because of the missing SUNWscn-base package. I manage three SPARC Solaris 10 computers. Two of these have Solaris 10 6/06 and the only one which has failed to install this patch has Solaris 10 1/06.
Rye at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 10
Dear Rye,Are you seeing the same errors indicated above in the discussion?Anything regardin an Unknown Host Exception ?If so please post what the system uses for name resolution.Mod.
ForumModerator at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 11
We have the same problem installing the patch 124614-01.
sysunipg at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 12
Hi all.Patch 124614-01 is only relevant to Solaris 10 6/06 (and possibly later), since the SUNWscn-base package was introduced then.I am enquiring on our internal lists to find out why it is being recommended on other releases.Mod.
ForumModerator at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 13
Hi all,I have the same issue with Patch 124614-01. I am using DNS for name resolution.Sincerely,Eck
Eckhard at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 14
Ok - Feb 23 and we STILL don't have a fix for this ?
su_A_ve at 2007-7-7 3:49:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 15
This issue has been esclated to the appropriate support group, and we are awaiting their recommendations.We will update this thread as soon as we have received any useful information.
ForumModeratora at 2007-7-21 15:33:00 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 16
For your information bug 6494650 that was raised for the 124615-01 being incorrectly recommended for sparc systems has been fixed.The metadata for patch 124615-01 is now marked correctly.
ForumModeratora at 2007-7-21 15:33:00 > top of Java-index,Administration Tools,Sun Update Connection-System...