HP Tru64 UNIX and TruCluster Server Version 5.1.B-4 Patch Summary and Release Notes (13156)

4.1.4 Unrecoverable Failure Procedure
The procedure to follow if you encounter unrecoverable failures while running dupatch during
a rolling upgrade has changed. The new procedure calls for you to run the clu_upgrade -undo
install command and then set the system baseline. The procedure is explained in the Patch
Kit Installation Instructions as notes in Section 5.3 and Section 5.6.
4.1.5 Do Not Add or Delete OSF, TCR, IOS, or OSH Subsets During Roll
During a rolling upgrade, do not use the /usr/sbin/setld command to add or delete any of
the following subsets:
• Base Operating System subsets (those with the prefix OSF).
• TruCluster Server subsets (those with the prefix TCR).
• Worldwide Language Support (WLS) subsets (those with the prefix IOS).
• New Hardware Delivery (NHD) subsets (those with the prefix OSH).
Adding or deleting these subsets during a roll creates inconsistencies in the tagged files.
4.1.6 Undo Stages in Correct Order
If you need to undo the install stage, because the lead member is in an unrecoverable state, be
sure to undo the stages in the correct order.
During the install stage, clu_upgrade cannot tell whether the roll is going forward or backward.
This ambiguity incorrectly allows the clu_upgrade undo preinstall stage to be run before
clu_upgrade undo install. Refer to the Patch Kit Installation Instructions for additional
information on undoing a rolling patch.
4.1.7 clu_upgrade undo of Install Stage Can Result in Incorrect File Permissions
This note applies only when both of the following are true:
• You are using installupdate, dupatch, or nhd_install to perform a rolling upgrade.
• You need to undo the install stage; that is, to use the clu_upgrade undo install
command.
In this situation, incorrect file permissions can be set for files on the lead member. This can result
in the failure of rsh, rlogin, and other commands that assume user IDs or identities by means
of setuid.
The clu_upgrade undo install command must be run from a nonlead member that has
access to the lead member's boot disk. After the command completes, follow these steps:
1. Boot the lead member to single-user mode.
2. Run the following script:
#!/usr/bin/ksh -p
#
# Script for restoring installed permissions
#
cd /
for i in /usr/.smdb./$(OSF|TCR|IOS|OSH)*.sts
do
grep -q "_INSTALLED" $i 2>/dev/null && /usr/lbin/fverify -y <"${i%.sts}.inv"
done
3. Rerun installupdate, dupatch, or nhd_install, whichever is appropriate, and complete
the rolling upgrade.
For information about rolling upgrades, see the Patch Kit Installation Instructions and the
installupdate(8) and clu_upgrade(8) reference pages.
148 TruCluster Server Patches