* * * READ ME * * *
                          * * * CPI 7.2 * * *
                         * * * Patch 400 * * *
                         Patch Date: 2018-07-17


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
CPI 7.2 Patch 400


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
AIX
RHEL6 x86-64
RHEL7 x86-64
SLES11 x86-64
SLES12 x86-64
Solaris 11 SPARC
Solaris 11 X86



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Availability 7.2
   * InfoScale Enterprise 7.2
   * InfoScale Foundation 7.2
   * InfoScale Storage 7.2


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.2.0.400
* 3904944 (3904943) The installer fails to recognize SLES 12 SP2.
* 3944949 (3944951) If vxcloudd is running, an attempt to upgrade the product
from 6.2.1 to 7.2 is unsuccessful.
* 3951378 (3951376) When you provide the "-patch_path" argument to the installer during a
rolling upgrade, the CPI performs a patch upgrade instead of first performing
phase 2 of the rolling upgrade.
* 3954439 (3954440) Rolling upgrade fails if a patch is installed as a part of Rolling
upgrade Phase1.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following incidents:

Patch ID: 7.2.0.400

* 3904944 (Tracking ID: 3904943)

SYMPTOM:
The installer fails with the error message 'No padv object defined for padv 
SLESx8664 for system on Sles12 SP2.

DESCRIPTION:
The installer fails with the error message 'No padv object defined for padv 
SLESx8664 for system' on Sles12 SP2.

RESOLUTION:
The installer code is modified to resolve the issue.

* 3944949 (Tracking ID: 3944951)

SYMPTOM:
If the vxcloud service (vxvm-vxcloud) is running, an attempt to upgrade
the product from 6.2.1 to 7.2 is unsuccessful.

DESCRIPTION:
The vxspec, vxdmp, and vxio modules cannot be unloaded while
vxcloudd is running. The InfoScale 7.2 CPI does not stop vxcloudd, and therefore
an upgrade performed using this installer fails.

RESOLUTION:
This hotfix updates the CPI to fix this issue so that the 7.2
installer stops vxcloudd before proceeding the upgrade tasks.

* 3951378 (Tracking ID: 3951376)

SYMPTOM:
When you provide the "-patch_path" argument to the installer during a
rolling upgrade, the CPI performs a patch upgrade instead of first performing
phase 2 of the rolling upgrade.

DESCRIPTION:
This issue occurs because the CPI fails to detect the installed
product state correctly during the rolling upgrade phase 2 checks. It then
directly proceeds to perform the patch upgrade tasks without first performing
phase 2 of the rolling upgrade. For example: If CPI finds that the InfoScale 7.2
VRTSvxvm package is installed on the system, it assumes that InfoScale 7.2 is
already installed. It then proceeds to perform the patch upgrade even though
phase 2 of the rolling upgrade from (say) SFHA 6.2.1 is not yet complete.

RESOLUTION:
The installer is updated to correctly detect the installed product
state during the rolling upgrade phase 2 checks, and accordingly proceed to
perform either phase 2 or the patch upgrades.

* 3954439 (Tracking ID: 3954440)

SYMPTOM:
When a patch is installed as a part of rolling upgrade Phase1, the rolling
upgrade fails with the error:
A more recent version of InfoScale Enterprise, 7.2.0.xxx, is already
installed.

DESCRIPTION:
When a patch is installed as a part of rolling upgrade Phase1, the kernel
package version might get upgraded to a version that is higher than the version
considered for upgrade. 

This results in failure of the rolling upgrade with the error:  A
more recent version of InfoScale Enterprise, 7.2.0.xxx, is already
installed.

RESOLUTION:
The CPI rolling upgrade prerequisites are modified to continue even if a patch
for InfoScale product is installed as part of Rolling upgrade Phase1.



INSTALLING THE PATCH
--------------------
1. Copy the hot-fix CPI_7.2.0_P4.pl to /tmp
2. Run installation scripts with the hot-fix
Example:
./installer -require /tmp/CPI_7.2.0_P4.pl


REMOVING THE PATCH
------------------
NONE


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE