README VERSION : 1.1 README CREATION DATE : 2015-04-06 PATCH-ID : VRTSvxfen-6.2.1.000 PATCH NAME : VRTSvxfen 6.2.1.000 BASE PACKAGE NAME : VRTSvxfen BASE PACKAGE VERSION : 6.2.0.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : rhel6_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : YES ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : YES PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Install Guide for install instructions and Release Notes for other information. PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Install Guide for uninstall instructions and Release Notes for other information. SPECIAL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:VRTSvxfen-6.2.1.000 3691204 (3691202) Sometimes fencing in the customized mode fails to start when the number of files present in the current working directory is large. 3714463 (3722178) The rpm --verify command on VXFEN changes the runlevel settings for the VXFEN service. SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:VRTSvxfen-6.2.1.000 * INCIDENT NO:3691204 TRACKING ID:3691202 SYMPTOM: Sometimes fencing fails to start and reports an error that it was unable to register with majority of coordination points. DESCRIPTION: The failure was observed due to an issue in the fencing startup script where a wildcard expansion in an echo expression produced some undesired value. The undesired value caused the fencing startup failure. RESOLUTION: The fencing code is modified so that the wildcard in the echo expression is does not get expanded. * INCIDENT NO:3714463 TRACKING ID:3722178 SYMPTOM: The runlevel setting for VXFEN service changes upon running the rpm --verify command on VXFEN. DESCRIPTION: The unexpected behavior is observed due to an issue in the VXFEN spec file which was turning on the VXFEN service. RESOLUTION: The VXFEN spec file code is modified so that the runlevel settings of VXFEN service are not modified during the verification phase. INCIDENTS FROM OLD PATCHES: --------------------------- NONE