United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6618779 servicetag not created for PACKAGE installation on Solaris (x86 and sparc)
6618779 : servicetag not created for PACKAGE installation on Solaris (x86 and sparc)

Details
Type:
Bug
Submit Date:
2007-10-18
Status:
Resolved
Updated Date:
2010-10-15
Project Name:
JDK
Resolved Date:
2007-10-26
Component:
infrastructure
OS:
solaris_10
Sub-Component:
build
CPU:
sparc
Priority:
P1
Resolution:
Fixed
Affected Versions:
6u4
Fixed Versions:
6u4

Related Reports
Relates:
JDK-6623024 - 64-bit JDK packages installation does not create servicetag

Sub Tasks

Description
This can be reproduced on Solaris 10 (x86 and sparc). This is a regression from b03. 

Basically, service tag file (/usr/jdk/instances/jdk1.6.0/jre/lib/servicetag) is not created
when installing jdk using the packages. 
Pre-requisite package stclient was installed prior to jdk packages installation.

Quick look at the postinstall and preremove scripts in SUNWj6rt package reveal that the
code relating to servicetag is missing. This code existed in b03. 
See missing code in b05 below:

if [ "${PKG_INSTALL_ROOT}" = "" ]; then
    ${INSTALL_NAME}/bin/java com.sun.servicetag.Installer -source "${PKGINST}"
    if [ -f ${INSTALL_NAME}/jre/lib/servicetag ]; then
        $INSTALLF -c none $PKGINST ${INSTALL_NAME}/jre/lib/servicetag
    fi
fi


While installing JDK using jdk.sh bundle,  servicetag file is created and
the registry populated accordingly.

Comments
EVALUATION

The freshbit process does not update the install directory of a package.

I modified the freshbit wrapper to add the postinstall/preremove after the freshbit script completes.
2007-10-26 
EVALUATION

Seems to be a build issue, reassigning to RE group for
further evaluation.
*** (#1 of 1): [ UNSAVED ] ###@###.###
2007-10-18 
EVALUATION

Looking at the Solaris packages for 6u4 b04/b05, and it appears
that there is a bug and/or feature in the patch creation process.

The Solaris patches we created for 6u4 has the ServiceTag
code in it's version of the postinstall script, so those should be
fine.

But the freshbit process (taking patches and creates
regular packages that look as if they've been patched)
doesn't seem to update the install directory of the packages,
which means the freshbit packages end up with the JDK6 GA
postinstall scripts.

I'll need to check with the owners of the scripts
(Solaris ON group) and see if it's by design that
nothing in the install directory of a packages seems
to be update in the freshbit process, or if it's a bug.
2007-10-18 
EVALUATION

Left out an important part of my analysis, since this problem
occurs in processing post build, what ever fix I come up
with will not be part of any respin build, and in fact, if this
is the only stopper for 6u4, then no respin will be needed.
2007-10-18


Hardware and Software, Engineered to Work Together