-
Bug
-
Resolution: Won't Fix
-
P3
-
6u12
-
generic
-
linux
OS : Linux
Hardware : any
Package : RPM only
Test spec : http://sqeweb.sfbay/deployment1/SQE/testing/ServiceTag/ServiceTagTestSpec.html
Test case : STS005.
When JDK is installed from RPM bundle to non-default location (by using "--prefix=" option), and then ST is registered by com.sun.servicetag.Installer, and then JDK is removed by "rpm -e", directory ${JAVA_HOME}/jre/lib/servicetag is remained unremoved, with registration.xml and servicetag files in it. Servicetag entry is removed from database successfully (stclient -g -i $URN command to check).
This is not a regression, same behavior can be seen with 6u10 (where servicetag feauture was firstly integrated).
Hardware : any
Package : RPM only
Test spec : http://sqeweb.sfbay/deployment1/SQE/testing/ServiceTag/ServiceTagTestSpec.html
Test case : STS005.
When JDK is installed from RPM bundle to non-default location (by using "--prefix=" option), and then ST is registered by com.sun.servicetag.Installer, and then JDK is removed by "rpm -e", directory ${JAVA_HOME}/jre/lib/servicetag is remained unremoved, with registration.xml and servicetag files in it. Servicetag entry is removed from database successfully (stclient -g -i $URN command to check).
This is not a regression, same behavior can be seen with 6u10 (where servicetag feauture was firstly integrated).