Hakim,
Based on what you supplied I would still think it would be disk space (required in both /tmp and /opt) but its hard to tell. And since you already "extracting the ssg-9.2.00-7581_CR06.noarch.rpm from the package and install it" I dont think we will be able to get to a specific root cause but if you have a problem in CR7 I would suggest a slightly different approach before installing the rpm and opening a support case.
The fact that your logs have the
patch install: Running shell script
Indicates the shell script for patching is running.
The
Patch install: Preparing... ####
Indicates that likely rpm o/s command is running the #### are similar to what you would see in the rpm -Uhv.
So since you seem to already mention you unzipped the SSGPatch.L7P
I would suggest next time running,
cd /com/l7tech/server/processcontroller/patching/builder/ShellScriptPatchTask_2
then run the shell in debug,
sh -x ./install.sh /{filetempextractfolder}/com/l7tech/server/processcontroller/patching/builder/ResourcesPatchTask_1
It seems from your output it likely passed to at least here,
RPMS_TO_INSTALL=$(eval ls ${PATCH_TMP}/ssg-${INSTALLING_GATEWAY_VERSION}*.rpm ${PATCH_TMP}/ssg-appliance-${INSTALLING_APPLIANCE_VERSION}*.${ARCH}.rpm)
# install the RPMs
/bin/rpm -Uvh $RPMS_TO_INSTALL
So I suspect the original rpm -Uhv was failing with multiple packages at the same time.
I have previously opened a case for better return code checking of this script internally to add more evaluations to the last return code $?
But I suggest if there are any issues with CR7 to open a support case and run the install.sh in debug as noted above.
Thanks, Charlie.