cpi-Patch-7.4.2.1000
Obsolete
The latest patch(es) : cpi-Patch-7.4.2.1100 

 Basic information
Release type: Patch
Release date: 2021-06-11
OS update support: None
Technote: None
Documentation: None
Popularity: 42 viewed    0 downloaded
Download size: 30.12 KB
Checksum: 2437271808

 Applies to one or more of the following products:
InfoScale Availability 7.4.2 On AIX 7.1
InfoScale Availability 7.4.2 On AIX 7.2
InfoScale Availability 7.4.2 On RHEL7 x86-64
InfoScale Availability 7.4.2 On RHEL8 x86-64
InfoScale Availability 7.4.2 On SLES12 x86-64
InfoScale Availability 7.4.2 On SLES15 x86-64
InfoScale Availability 7.4.2 On Solaris 11 SPARC
InfoScale Availability 7.4.2 On Solaris 11 X64
InfoScale Enterprise 7.4.2 On AIX 7.1
InfoScale Enterprise 7.4.2 On AIX 7.2
InfoScale Enterprise 7.4.2 On RHEL7 x86-64
InfoScale Enterprise 7.4.2 On RHEL8 x86-64
InfoScale Enterprise 7.4.2 On SLES12 x86-64
InfoScale Enterprise 7.4.2 On SLES15 x86-64
InfoScale Enterprise 7.4.2 On Solaris 11 SPARC
InfoScale Enterprise 7.4.2 On Solaris 11 X64
InfoScale Foundation 7.4.2 On AIX 7.1
InfoScale Foundation 7.4.2 On AIX 7.2
InfoScale Foundation 7.4.2 On RHEL7 x86-64
InfoScale Foundation 7.4.2 On RHEL8 x86-64
InfoScale Foundation 7.4.2 On SLES12 x86-64
InfoScale Foundation 7.4.2 On SLES15 x86-64
InfoScale Foundation 7.4.2 On Solaris 11 SPARC
InfoScale Foundation 7.4.2 On Solaris 11 X64
InfoScale Storage 7.4.2 On AIX 7.1
InfoScale Storage 7.4.2 On AIX 7.2
InfoScale Storage 7.4.2 On RHEL7 x86-64
InfoScale Storage 7.4.2 On RHEL8 x86-64
InfoScale Storage 7.4.2 On SLES12 x86-64
InfoScale Storage 7.4.2 On SLES15 x86-64
InfoScale Storage 7.4.2 On Solaris 11 SPARC
InfoScale Storage 7.4.2 On Solaris 11 X64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:

This patch is obsolete. It is superseded by: Release date
cpi-Patch-7.4.2.1100 2021-06-18

This patch supersedes the following patches: Release date
cpi-Patch-7.4.2.900 (obsolete) 2021-06-09
cpi-Patch-7.4.2.800 (obsolete) 2021-04-20
cpi-Patch-7.4.2.700 (obsolete) 2021-02-22
cpi-Patch-7.4.2.600 (obsolete) 2021-01-18
cpi-Patch-7.4.2.500 (obsolete) 2021-01-11
cpi-Patch-7.4.2.400 (obsolete) 2020-11-12
cpi-Patch-7.4.2.300 (obsolete) 2020-10-09
cpi-Patch-7.4.2.200 (obsolete) 2020-07-27
cpi-Patch-7.4.2.100 (obsolete) 2020-07-07

 Fixes the following incidents:
4006619, 4008502, 4010025, 4012032, 4013446, 4014920, 4014985, 4016078, 4020090, 4021517, 4022492, 4027741, 4033243, 4033688, 4034357, 4038945, 4040836

 Patch ID:
None.

Readme file
                          * * * READ ME * * *
                         * * * CPI 7.4.2 * * *
                         * * * Patch 1000 * * *
                         Patch Date: 2021-06-11


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.4.2 Patch 1000


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



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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.4.2.1000
* 4006619 (4015976) On a Solaris system, patch upgrade of InfoScale fails with an error in the alternate boot environment.
* 4008502 (4008744) Rolling upgrade using response file fails if one or more operating system packages are missing on the cluster nodes.
* 4010025 (4010024) While upgrading from InfoScale 7.4.2 to 7.4.2.xxx, CPI installs the packages from the 7.4.2.xxx patch only and not the base packages of 7.4.2 GA.
* 4012032 (4012031) Installer does not upgrade VRTSvxfs and VRTSodm inside
non-global zones
* 4013446 (4008578) Even though a cluster node may have a fully qualified hostname, the product installer trims this value and uses the shorter hostname for the cluster configuration.
* 4014920 (4015139) Product installer fails to install InfoScale on RHEL 8 systems if IPv6 addresses are provided for the system list.
* 4014985 (4014983) The product installer does not display a warning at the time of the pre-upgrade check to suggest that you will need to provide telemetry details later on if the cluster nodes are not registered with TES or VCR.
* 4016078 (4007633) The product installer fails to synchronize the system clocks with the NTP server.
* 4020090 (4022920) The product installer fails to install InfoScale 7.4.2 on SLES 15 SP2.
* 4021517 (4021515) On SLES 12 SP4 and later systems, the installer fails to fetch the media speed of the network interfaces.
* 4022492 (4022640) Installer fails to complete installation after it automatically downloads a required support patch from SORT that contains a VRTSvlic package.
* 4027741 (4027759) The product installer installs lower versions packages if multiple patch bundles are specified using the patch path options in the incorrect order.
* 4033243 (4033242) When a responsefile is used, the product installer fails to add the required VCS users.
* 4033688 (4033687) The InfoScale product installer deletes any existing cluster configuration files during uninstallation.
* 4034357 (4033988) The product installer does not allow the installation of an Infoscale patch bundle if a more recent version of any package in the bundle is already installed on the system.
* 4038945 (4033957) The VRTSveki and the VRTSvxfs RPMs fail to upgrade when using yum.
* 4040836 (4040833) After an InfoScale upgrade to version 7.4.2 Update 2 on Solaris, the latest vxfs module is not loaded.


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

Patch ID: 7.4.2.1000

* 4006619 (Tracking ID: 4015976)

SYMPTOM:
On a Solaris system, patch upgrade of InfoScale fails with an error in the alternate boot environment.

DESCRIPTION:
InfoScale does not support patch upgrade in alternate boot environments. Therefore, when you provide the "-rootpath" argument to the installer during a patch upgrade, the patch upgrade operation fails with the following error message: CPI ERROR V-9-0-0 The -rootpath option works only with upgrade tasks.

RESOLUTION:
The installer is enhanced to support patch upgrades in alternate boot environments by using the -rootpath option.

* 4008502 (Tracking ID: 4008744)

SYMPTOM:
Rolling upgrade using response file fails if one or more operating system packages are missing on the cluster nodes.

DESCRIPTION:
When rolling upgrade is performed using response file, the installer script checks for the missing operating system packages and installs them. After installing the missing packages on the cluster nodes, the installer script fails and exit. The following error message is logged:
CPI ERROR V-9-40-1153 Response file error, no configuration for rolling upgrade phase 1.
This issue occurs because the installer script fails to check the sub-cluster numbers in the response file.

RESOLUTION:
The installer script is enhanced to continue with the rolling upgrade after installing the missing OS packages on the cluster nodes.

* 4010025 (Tracking ID: 4010024)

SYMPTOM:
CPI assumes that the third digit in an InfoScale 7.4.2 version indicates a patch version, and not a GA version. Therefore, it upgrades the packages from the patch only and does not upgrade the base packages.

DESCRIPTION:
To compare product versions and to set the type of installation, CPI compares the currently installed version with the target version to be installed. However, instead of comparing all the digits in a version, it incorrectly compares only the first two digits. In this case, CPI compares 7.4 with 7.4.2.xxx, and finds that the first 2 digits match exactly. Therefore, it assumes that the base version is already installed and then installs the patch packages only.

RESOLUTION:
This hotfix updates the CPI to recognize InfoScale 7.4.2 as a base version and 7.4.2.xxx (for example) as a patch version. After you apply this patch, CPI can properly upgrade the base packages first, and then proceed to upgrade the packages that are in the patch.

* 4012032 (Tracking ID: 4012031)

SYMPTOM:
If older versions of the VRTSvxfs and VRTSodm packages are installed in
non-global zones, they are not 
upgraded when upgrade to a newer version of the product.

DESCRIPTION:
If older versions of the VRTSvxfs and VRTSodm packages are installed in
non-global zones, you must 
uninstall them before you perform a product upgrade. After you upgrade those
packages in global zones, you 
must then install the VRTSvxfs and VRTSodm packages manaully in the non-global
zones.

RESOLUTION:
The CPI will handle the VRTSodm and VRTSvxfs package in non-global zone in the
same manner it does in global zone.

* 4013446 (Tracking ID: 4008578)

SYMPTOM:
Even though a cluster node may have a fully qualified hostname, the product installer trims this value and uses the shorter hostname for the cluster configuration.

DESCRIPTION:
The name of a cluster node may be set to a fully qualified hostname, for example, somehost.example.com. However, by default, the product installer trims this value and uses the shorter hostname (for example, somehost) for the cluster configuration.

RESOLUTION:
This hotfix updates the installer to allow the use of the new "-fqdn" option. If this option is specified, the installer uses the fully qualified hostname for cluster configuration. Otherwise, the installer continues with the default behavior.

* 4014920 (Tracking ID: 4015139)

SYMPTOM:
If IPv6 addresses are provided for the system list on a RHEL 8 system, the product installer fails to verify the network communication with the remote systems and cannot proceed with the installation. The following error is logged:
CPI ERROR V-9-20-1104 Cannot ping <IPv6_address>. Please make sure that:
        - Provided hostname is correct
        - System <IPv6_address> is in same network and reachable
        - 'ping' command is available to use (provided by 'iputils' package)

DESCRIPTION:
This issue occurs because the installer uses the ping6 command to verify the communication with the remote systems if IPv6 addresses are provided for the system list. For RHEL 8 and its minor versions, the path for ping6 has changed from /bin/ping6 to /sbin/ping6, but the installer uses the old path.

RESOLUTION:
This hotfix updates the installer to use the correct path for the ping6 command.

* 4014985 (Tracking ID: 4014983)

SYMPTOM:
The product installer does not display a warning at the time of the pre-upgrade check to suggest that you will need to provide telemetry details later on if the cluster nodes are not registered with TES or VCR.

DESCRIPTION:
The product installer prompts you to provide the telemetry details of cluster nodes after upgrading the InfoScale packages but before starting the services. If you cancel the installation at this stage, the Cluster Server resources cannot be brought online. Therefore, a warning message is required during the pre-upgrade checks to remind you to keep these details ready.

RESOLUTION:
The product installer is updated to notify you at the time of the pre-upgrade check, that if the cluster nodes are not registered with TES or VCR, you will need to provide these telemetry details later on.

* 4016078 (Tracking ID: 4007633)

SYMPTOM:
The product installer fails to synchronize the system clocks with the NTP server.

DESCRIPTION:
This issue occurs when the /usr/sbin/ntpdate file is missing on the systems where the clocks need to be synchronized.

RESOLUTION:
Updated the installer to include a dependency on the ntpdate package, which helps the system clocks to be synchronized with the NTP server.

* 4020090 (Tracking ID: 4022920)

SYMPTOM:
The product installer fails to install InfoScale 7.4.2 on SLES 15 SP2 and displays the following error message: 
CPI ERROR V-9-0-0
0 No padv object defined for padv SLESx8664 for system <system_name>

DESCRIPTION:
This issue occurs because the format of the kernel version that is required by SLES 15 SP2 is not included.

RESOLUTION:
The installer is updated to include the format of the kernel version that is required to support installation on SLES 15 SP2.

* 4021517 (Tracking ID: 4021515)

SYMPTOM:
On SLES 12 SP4 and later systems, the installer fails to fetch the media speed of the network interfaces.

DESCRIPTION:
The path of the 'ethtool' command is changed in SLES 12 SP4. Therefore, on SLES 12 SP4 and later systems, the installer does not recognize the changed path and uses an incorrect path '/sbin/ethtool' instead of '/usr/sbin/ethtool' for the 'ethtool' command. Consequently, while configuring the product, the installer fails to fetch the media speed of the network interfaces and displays its value as "Unknown".

RESOLUTION:
This hotfix updates the installer to use the correct path for the 'ethtool' command.

* 4022492 (Tracking ID: 4022640)

SYMPTOM:
The product installer fails to complete the installation after it automatically downloads a required support patch from SORT that contains a VRTSvlic package. The following error is logged:
CPI ERROR V-9-0-0
0 No pkg object defined for pkg VRTSvlic401742 and padv <<PADV>>

DESCRIPTION:
During installation, the product installer looks for any applicable platform support patches that are available on SORT and automatically downloads them. However, it fails to correctly identify the base version of the VRTSvlic package on the system to compare it with the downloaded version. Consequently, even though the appropriate patch is available, the installer fails to complete the installation.

RESOLUTION:
To address this issue, the product installer is updated to correctly identify the base version of the VRTSvlic package on a system.

* 4027741 (Tracking ID: 4027759)

SYMPTOM:
The product installer installs lower versions packages if multiple patch bundles are specified using the patch path options in the incorrect order.

DESCRIPTION:
The product installer expects that the patch bundles, if any, are specified in the lower-to-higher order. Consequently, the installer always overrides the package version from the available package in the last patch bundle in which it exists. If patch bundles are not specified in the expected order, installer installs last available version for a component package.

RESOLUTION:
To address this issue, the product installer is updated to correctly identify the higher package version before installing the patch bundles. It does so regardless of the order in which the patch bundles are specified.

* 4033243 (Tracking ID: 4033242)

SYMPTOM:
When a responsefile is used, the product installer fails to add the required VCS users.

DESCRIPTION:
The product installer fails to add the required VCS users during configuration, if a responsefile is used to provide the corresponding input.

RESOLUTION:
This patch updates the installer so that it adds the required VCS users while using a responsefile for configuration.

* 4033688 (Tracking ID: 4033687)

SYMPTOM:
The InfoScale product installer deletes any existing cluster configuration files during uninstallation.

DESCRIPTION:
During uninstallation, the product installer deletes cluster configuration files like /etc/llthosts, /etc/llttab, and so on. Consequently, when you reinstall the InfoScale product, you need to perform all the cluster configuration procedures again.

RESOLUTION:
This patch updates the product installer so that it no longer deletes any existing cluster configuration files. Consequently, you can reconfigure the clusters quickly by using the existing configuration files.

* 4034357 (Tracking ID: 4033988)

SYMPTOM:
The product installer displays the following error message after the precheck and does not allow you to proceed with the installation:
The higher version of <package_name> is already installed on <system_name>

DESCRIPTION:
The product installer compares the versions of the packages in an Infoscale patch bundle with those of the packages that are installed on a system. If a more recent version of any of the packages in the bundle is found to be already installed on the system, the installer displays an error. It does not allow you to proceed further with the installation.

RESOLUTION:
The product installer is updated to allow the installation of an Infoscale patch bundle that may contain older versions of some packages. Instead of an error message, the installer now displays a warning message and lets you proceed with the installation.

* 4038945 (Tracking ID: 4033957)

SYMPTOM:
The VRTSveki and the VRTSvxfs RPMs fail to upgrade when using yum.

DESCRIPTION:
The product installer assumes that services are stopped if the corresponding modules are unloaded. However, the veki and the vxfs services remain active even after the modules are unloaded, which causes the RPMs to fail during the upgrade.

RESOLUTION:
The installer is enhanced to stop the veki and the vxfs services when the modules are unloaded but the services remain active.

* 4040836 (Tracking ID: 4040833)

SYMPTOM:
After an InfoScale upgrade to version 7.4.2 Update 2 on Solaris, the latest vxfs module is not loaded.

DESCRIPTION:
This issue occurs when the patch_path option of the product installer is used to perform the upgrade. When patch_path is used, the older versions of the packages in the patch are not uninstalled. Thus, the older version of the vxfs package gets loaded after the installation.

RESOLUTION:
This hotfix updates the product installer to address this issue with the patch_path option. When patch_path is used, the newer versions of the packages in the patch are installed only after the corresponding older packages are uninstalled.



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


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


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


OTHERS
------
NONE
Read and accept Terms of Service