Patch 120292-01 Failed.
portal says that this patch failed, however the log on the server itself says (in /var/sadm/patch/120292-01):
Package not patched:
PKG=SUNWmysqlS
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWmysqlr> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWmysqlt> was successful.
In /var/sadm/spool I have:
root@vcs01:[spool]$ ls
119107-03.jar120292-01.jar.dir disallowed_patch_list_report
120292-01.jarcache patchproSequester
And the patch file is not listed in disallowed_patch_list_report either.
I have 2 test systems that were built exactly the same and they're both showing the same failure. Original install was Solaris 10 (the GA release) with the cluster SUNWCall and were built via jumpstart. Have another system built with the SUNWCXall cluster from the same jumpstart server and it does not report as failed.
Is the portal referring to the "S" package?
[2099 byte] By [
dyoung2] at [2007-11-26 6:03:35]
# 1
I installed that patch successfully on a zoneless machine with smpatch update.
But on a zoned machine where I have to install patches using patchadd, so I can see the output, I got the same kind of error messages.
I'm also concerned about patch 118550-04.
On the global zone, I got the following error
Version of package SUNWcakr from patch 118550-04 differs from the package installed on the system.
And on the zones I got this different error
The original package SUNWcakr.u that 118550-04 is attempting to install to does not exist on this system.
The original package SUNWcakr.us that 118550-04 is attempting to install to does not exist on this system.
# 2
The portal reports the patch install status based on the information sent over from the system the install is conducted. When the portal report a failure on a subtask(a patch install on a particular system is a subtask), there should be a message related to this faliure. To help us to further debug from the portal side, we need the original submitter to obtain following information:
1) Click on the "Jobs" tab to viem the task list,
2) Checkbox the job with the failed patch install,
3) Click on "View Jobs" button in the table header or table bottom,
4) In the 'Jobs Detail' table, check whethere there is any message in the 'Comments' column associated with the the system that the patch failed to install. If there is, post back to this thread the message,
5) run the command '/usr/sbin/smpatch list | grep 120292-01'
to see whether the patch is truely installed.
Thanks!
Wenzhou Wang
# 4
I have setup my system trying to reproduce the issue you saw, but I don't see this patch as available from either the portal or the UM. My configuration is as this:
Sparc Ultra 60; Solaris 10 GA(s10_74L2a); Entire Software group(SUNWCall). Seems that this patch might not be generic, meaning, it only apply to certain software group(for exampe SUNWCxall), or you installed some extra software on the system. Could you give a little more detail information as what platform, what software group, and how do you installed the patch(from UM, portal, etc) when you see the failed status so that we can reproduce, then trace down from the portal to the Update Manager/smpatch to make sure that portal report the status correctly and there is no issue here.
Thanks!
Wenzhou
# 5
2 systems had the same issue. They are both Ultra 10's loaded from Jumpstart. The installed Solaris 10 image release file reads:
root@vcs01:[root]$ cat /etc/release
Solaris 10 3/05 s10_74L2a SPARC
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 22 January 2005
Here's the jumpstart profile used for those systems:
# =============================================================================
#
# SYSTEM : vcs01
# RAM: 256MB
# DISK 0 :
#
# =============================================================================
#
# vim:set noexpandtab:
# vim:set ts=8:
#
# =============================================================================
install_typeinitial_install
cluster SUNWCall
partitioningexplicit
filesys rootdisk.s6 512 swap
filesys rootdisk.s0 free/
# jumpstart server
filesys jumphost:/jumpstart - /jumpstart ro,soft,intr,actimeo=0
I installed the patch from the portal. After I initially registered the system I went into the portal and said to apply all updates. After the ones that could be installed were installed, I did an init 6 and let it run through the remainder. After it came back up is when the patch showed as failed on the portal. Oh, and the jar file and the jar.dir was still left in /var/sadm/spool.
It seems as though it's the SUNWCall cluster that does/did make this happen. 2 other systems I have I loaded with SUNWCprog and did not have the same issue.
