cpi-Patch-7.4.2.3100

 Basic information
Release type: Patch
Release date: 2023-01-03
OS update support: None
Technote: None
Documentation: None
Popularity: 123 viewed    downloaded
Download size: 79.25 KB
Checksum: 45569420

 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 supersedes the following patches: Release date
cpi-Patch-7.4.2.3000 (obsolete) 2022-10-20
cpi-Patch-7.4.2.2900 (obsolete) 2022-10-10
cpi-Patch-7.4.2.2800 (obsolete) 2022-09-27
cpi-Patch-7.4.2.2700 (obsolete) 2022-09-18
cpi-Patch-7.4.2.2600 (obsolete) 2022-09-16
cpi-Patch-7.4.2.2500 (obsolete) 2022-08-23
cpi-Patch-7.4.2.2400 (obsolete) 2022-08-22
cpi-Patch-7.4.2.2300 (obsolete) 2022-07-24
cpi-Patch-7.4.2.2200 (obsolete) 2022-07-04
cpi-Patch-7.4.2.2100 (obsolete) 2022-06-30
cpi-Patch-7.4.2.2000 (obsolete) 2022-05-15
cpi-Patch-7.4.2.1900 (obsolete) 2022-02-28
cpi-Patch-7.4.2.1800 (obsolete) 2021-11-09
cpi-Patch-7.4.2.1700 (obsolete) 2021-10-19
cpi-Patch-7.4.2.1600 (obsolete) 2021-10-11
cpi-Patch-7.4.2.1500 (obsolete) 2021-10-05
cpi-Patch-7.4.2.1400 (obsolete) 2021-08-09
cpi-Patch-7.4.2.1300 (obsolete) 2021-07-13
cpi-Patch-7.4.2.1200 (obsolete) 2021-07-06
cpi-Patch-7.4.2.1100 (obsolete) 2021-06-18
cpi-Patch-7.4.2.1000 (obsolete) 2021-06-11
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, 4041770, 4042590, 4042890, 4043366, 4043372, 4043892, 4045881, 4046196, 4050467, 4052860, 4052867, 4053752, 4053875, 4053876, 4054322, 4054913, 4055055, 4066237, 4067433, 4070908, 4079500, 4079916, 4080100, 4081964, 4084977, 4085612, 4086047, 4086570, 4086624, 4087148, 4087809, 4089657, 4089815, 4092407, 4100693

 Patch ID:
None.

Readme file
                          * * * READ ME * * *
                         * * * CPI 7.4.2 * * *
                         * * * Patch 3100 * * *
                         Patch Date: 2022-12-23


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 3100


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.3100
* 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.
* 4041770 (4041816) On RHEL 8.4, the system panics after the InfoScale stack starts.
* 4042590 (4042591) On RHEL 8.4, installer disable IMF for the CFSMount and the Mount agents.
* 4042890 (4043075) After performing a phased upgrade of InfoScale, the product installer fails to update the types.cf file.
* 4043366 (4042674) The product installer does not honor the single-node mode of a cluster and restarts it in the multi-mode if 'vcs_allowcomms = 1'.
* 4043372 (4043371) If SecureBoot is enabled on the system, the product installer fails to install some InfoScale RPMs (VRTSvxvm, VRTSaslapm, VRTScavf).
* 4043892 (4043890) The product installer incorrectly prompts users to install deprecated OS RPMs for LLT over RDMA configurations.
* 4045881 (4043751) The VRTScps RPM installation may fail on SLES systems.
* 4046196 (4067426) Package uninstallation during a rolling upgrade fails if non-global zones are under VCS service group control
* 4050467 (4050465) The InfoScale product installer fails to create VCS users for non-secure clusters.
* 4052860 (4052859) The InfoScale product installer needs to install the VRTSpython package on AIX and Solaris.
* 4052867 (4052866) The InfoScale product installer needs to run the CollectorService process during a fresh configuration of VCS.
* 4053752 (4053753) The licensing service is upgraded to allow an InfoScale server to be registered with a Veritas Usage Insights server.
* 4053875 (4053635) The vxconfigd service fails to start during the add node operation when the InfoScale product installer is used to perform a fresh configuration on Linux.
* 4053876 (4053638) The installer prompt to mount shared volumes during an add node operation does not advise that the corresponding CFSMount entries will be updated in main.cf.
* 4054322 (4054460) InfoScale installer fails to start the GAB service with the -start option on Solaris.
* 4054913 (4054912) During upgrade, the product installer fails to stop the vxfs service.
* 4055055 (4055242) InfoScale installer fails to install a patch on Solaris.
* 4066237 (4057908) The product installer fails to configure passwordless SSH communication for remote Solaris systems.
* 4067433 (4067432) While upgrading to 7.4.2 Update 2 , VRTSvlic patch package installation fails.
* 4070908 (4071690) The installer does perform an Infoscale configuration without registering the Infoscale server to an edge server.
* 4079500 (4079853) Patch installer flashes a false error message with -precheck option.
* 4079916 (4079922) Installer fails to complete installation after it automatically downloads a required support patch from SORT that contains a VRTSperl package.
* 4080100 (4080098) Installer fails to complete the CP server configuration.
* 4081964 (4081963) VRTSvxfs patch fails to install on Linux platforms.
* 4084977 (4084975) Installer fails to complete the CP server configuration.
* 4085612 (4087319) On RHEL 7.4.2, Installer fails to uninstall VxVM while upgrading from 7.4.2 to 8.0U1.
* 4086047 (4086045) When Infoscale cluster is reconfigured, LLT, GAB, VXFEN services fail to start after reboot.
* 4086570 (4076583) On a Solaris system, the InfoScale installer runs set/unset publisher several times but does not disable 
the publisher. The deployment process slows down as a result.
* 4086624 (4086623) Installer fails to complete the CP server configuration.
* 4087148 (4088698) CPI installer tries to download a must-have patch whose version is lower than the version specified in media path.
* 4087809 (4086533) VRTSfsadv pkg fails to upgrade from 7.4.2 U4 to 8.0 U1 while using yum upgrade.
* 4089657 (4089934) Installer does not update the '/opt/VRTSvcs/conf/config/types.cf' file after a VRTSvcs patch upgrade.
* 4089815 (4089867) On Linux, Installer fails to start fsdedupschd service.
* 4092407 (4092408) On a Linux platform, CPI installer fails to correctly identify status of vxfs_replication service.
* 4100693 (4076583) On a Solaris system, the InfoScale installer runs set/unset publisher several times but does not disable 
the publisher. The deployment process slows down as a result.


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

Patch ID: 7.4.2.3100

* 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.

* 4041770 (Tracking ID: 4041816)

SYMPTOM:
On RHEL 8.4, the system panics after the InfoScale stack starts.

DESCRIPTION:
The system panics when the CFSMount agent or the Mount agent attempts to register for IMF. This issue occurs because these agents are IMF-enabled by default.

RESOLUTION:
This hotfix updates the product installer to disable IMF for the CFSMount and the Mount agents on RHEL 8.4 systems.

* 4042590 (Tracking ID: 4042591)

SYMPTOM:
On RHEL 8.4, installer disable IMF for the CFSMount and the Mount agents.

DESCRIPTION:
By default IMF for the CFSMount and the Mount agents are enabled. On RHEL 8.4, installer was used to disable IMF for the CFSMount and the Mount agents before starting the agents.

RESOLUTION:
This hotfix updates the product installer to not to disable IMF for the CFSMount and the Mount agents on RHEL 8.4 systems.

* 4042890 (Tracking ID: 4043075)

SYMPTOM:
After performing a phased upgrade of InfoScale, the product installer fails to update the types.cf file.

DESCRIPTION:
You can rename the /etc/llttab file before an OS upgrade and revert to the original configuration after the OS upgrade and before you start the InfoScale stack upgrade. However, if you do not revert the renamed /etc/llttab file, the product installer fails to identify that VCS is configured on the mentioned systems and proceeds with upgrade. Consequently, the installer does not update the .../config/types.cf file.

RESOLUTION:
This hotfix updates the product installer to avoid such a situation. It displays an error and exits after the precheck tasks if the /etc/llttab file is missing and the other VCS configuration files are available on the mentioned systems.

* 4043366 (Tracking ID: 4042674)

SYMPTOM:
The product installer does not honor the single-node mode of a cluster and restarts it in the multi-mode if 'vcs_allowcomms = 1'.

DESCRIPTION:
On a system where a single-node cluster is running, if you upgrade InfoScale using a response file with 'vcs_allowcomms = 1', the existing cluster configuration is not restored. The product installer restarts the cluster in the multi-node mode. When 'vcs_allowcomms = 1', the installer does not consider the value of the ONENODE parameter in the /etc/sysconfig/vcs file. It fails to identify that VCS is configured on the systems mentioned in the response file and proceeds with upgrade. Consequently, the installer neither updates the .../config/types.cf file nor restores the /etc/sysconfig/vcs file.

RESOLUTION:
This hotfix updates the product installer to honor the single-node mode of an existing cluster configuration on a system.

* 4043372 (Tracking ID: 4043371)

SYMPTOM:
If SecureBoot is enabled on the system, the product installer fails to install some InfoScale RPMs (VRTSvxvm, VRTSaslapm, VRTScavf).

DESCRIPTION:
InfoScale installations are not supported on systems where SecureBoot is enabled. However, the product installer does not check whether SecureBoot is enabled on the system. Consequently, it fails to install some InfoScale RPMs even though it proceeds with the installation.

RESOLUTION:
This hotfix updates the product installer to check whether SecureBoot is enabled, and if so, display an appropriate error message and exit.

* 4043892 (Tracking ID: 4043890)

SYMPTOM:
The product installer incorrectly prompts users to install deprecated OS RPMs for LLT over RDMA configurations.

DESCRIPTION:
The following RPMs that are used in LLT RDMA configurations have been deprecated: (1) the libmthca and the libmlx4 OS RPMs have been replaced by libibverbs, and (2) the rdma RPM has been replaced by rdma-core. However, even when the libibverbs and the rdma-core RPMs are installed on a system, the InfoScale installer prompts users to install the corresponding deprecated RPMs. Furthermore, if these deprecated RPMs are not installed, the installer does not allow users to proceed with the InfoScale cluster configuration.

RESOLUTION:
This hotfix updates the product installer to use the correct OS RPMs dependency list for LLT over RDMA configurations.

* 4045881 (Tracking ID: 4043751)

SYMPTOM:
The VRTScps RPM installation may fail on SLES systems.

DESCRIPTION:
The VRTScps RPM has a dependency on the "/etc/SUSE-brand" file that is available in the "branding-SLE" package. If the brand file is not present on the system, the InfoScale product installer may fail to install the VRTScps RPM on SLES systems.

RESOLUTION:
This hotfix adresses the issue by updating the product installer to include the "branding-SLE" package in OS dependency list during the installation pre-check.

* 4046196 (Tracking ID: 4067426)

SYMPTOM:
Package uninstallation during a rolling upgrade fails if non-global zones are under VCS service group control

DESCRIPTION:
During a Rolling upgrade, VCS failover service groups get switched to another machine in the cluster before upgrade starts. Installer checks whether any zone has Veritas packages installed on it and tries to uninstall the packages from the non-global zone before upgrading. Uninstall fails because non-global zone is not on the current machine but failover is on the machine which is not upgrading.

RESOLUTION:
Installer checks if any zone has Veritas packages installed and is under VCS service group control. In such a case, installer does not upgrade zone on the current machine because non-global zone switches to the other machine in the cluster.

* 4050467 (Tracking ID: 4050465)

SYMPTOM:
The InfoScale product installer fails to create VCS users for non-secure clusters.

DESCRIPTION:
In case of non-secure clusters, the product installer fails to locate the binary that is required for password encryption. Consequently, the addition of VCS users fails.

RESOLUTION:
The product installer is updated to be able to successfully create VCS users in case of non-secure clusters.

* 4052860 (Tracking ID: 4052859)

SYMPTOM:
The InfoScale licensing component on AIX and Solaris and the InfoScale agents for Pure Storage replication on AIX do not work if the VRTSPython package is not installed.

DESCRIPTION:
On AIX and Solaris, the VRTSpython package is required to support the InfoScale licensing component. On AIX, the VRTSpython package is required to support the InfoScale agents for Pure Storage replication. These components do not work because the InfoScale product installer does not install the VRTSPython module on AIX and Solaris.

RESOLUTION:
The product installer is enhanced to install the VRTSpython package on AIX and Solaris.

* 4052867 (Tracking ID: 4052866)

SYMPTOM:
After a fresh configuration of VCS, if the InfoScale cluster node is not registered with the Usage Insights service, the expected nagging messages do not get logged in the telemetry and the system logs.

DESCRIPTION:
The CollectorService process needs to be running during an installation or a configuration operation so that the InfoScale node can register itself with the Usage Insights service. This issue occurs because the product installer does not start the CollectorService process during a fresh configuration of VCS.

RESOLUTION:
The product installer is updated to start the CollectorService process during a fresh configuration of VCS.

* 4053752 (Tracking ID: 4053753)

SYMPTOM:
The InfoScale product installer prompts you to enter the host name or the IP address and the port number of a Usage Insights server instance.

DESCRIPTION:
The licensing service is upgraded to help manage your InfoScale licenses more effectively. As part of this upgrade, you can register an InfoScale server with an on-premises Usage Insights server in your data center. The product installer prompts you to enter the host name or the IP address and the port number of the Usage Insights server instance. Using this information, the installer registers the InfoScale server with the Usage Insights server.

RESOLUTION:
The product installer is enhanced to register InfoScale servers with a Veritas Usage Insights server.

* 4053875 (Tracking ID: 4053635)

SYMPTOM:
If a system is restarted immediately after the product installation, the vxconfigd service fails to start when an add node operation is initiated during a fresh configuration.

DESCRIPTION:
When a system is restarted immediately after product installation, the VxVM agent attempts to start the vxvm-boot service. The service does not started properly due to the presence of the install-db file on the system. During a product configuration (or the add node operation), the product installer removes the install-db file and attempts to start the vxvm-boot service. However, because the service was already in the active state, systemd does not execute the vxvm-startup scripts again. Consequently, both the 'vxdctl init' and the 'vxdctl enable' commands fail with the exit code '4'.

RESOLUTION:
The product installer is updated to first restart the vxvm-boot service and then start the vxconfigd service when a system is restarted.

* 4053876 (Tracking ID: 4053638)

SYMPTOM:
The installer prompt to mount shared volumes during an add node operation does not advise that the corresponding CFSMount entries will be updated in main.cf.

DESCRIPTION:
If any shared volumes are mounted on the existing cluster nodes, during the add node operation, the installer provides you an option to mount them on new nodes as well. If you choose to mount the shared volumes on the new nodes, the installer updates the corresponding CFSMount entries in the main.cf file. However, the installer prompt does not advise that main.cf will also be updated.

RESOLUTION:
The installer prompt is updated to advise that the CFSMount entries in main.cf will be updated if you choose to mount shared volumes on new nodes.

* 4054322 (Tracking ID: 4054460)

SYMPTOM:
InfoScale installer fails to start the GAB service with the -start option on Solaris.

DESCRIPTION:
The product installer removes the GAB driver when it stops the service with the -stop option. However, it does not add the GAB driver while starting the service with the -start option, so the GAB service fails to start.

RESOLUTION:
The product installer is updated to load the GAB driver before it attempts to start the GAB service.

* 4054913 (Tracking ID: 4054912)

SYMPTOM:
During upgrade, the product installer fails to stop the vxfs service.

DESCRIPTION:
If upgrading from lower than InfoScale 7.3 version, the product installer assumes that services are stopped if the corresponding modules are unloaded. However, 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 vxfs services when the modules are unloaded but the services remain active.

* 4055055 (Tracking ID: 4055242)

SYMPTOM:
InfoScale installer fails to install a patch on Solaris and displays the following error:
CPI ERROR V-9-0-0
0 Cannot find VRTSpython for padv Sol11sparc in <<media path>>

DESCRIPTION:
The product installer expects the VRTSpython patch to be available in the media path that is provided. When the patch is not available at the expected location, the installer fails to proceed and exits with the aforementioned error message.

RESOLUTION:
The product installer is updated to handle such a scenario and proceed to install the other available patches.

* 4066237 (Tracking ID: 4057908)

SYMPTOM:
The InfoScale product installer fails to configure passwordless SSH communication for remote Solaris systems that have one of these SRUs installed: 11.4.36.101.2 and 11.4.37.101.1.

DESCRIPTION:
To establish passwordless SSH communication with a remote system, the installer tries to fetch the home directory details of the remote system. This task fails due to an issue with the function that fetches those details. The product installation fails because the passwordless SSH communication is not established.

RESOLUTION:
The product installer is updated to address this issue so that the installation does not fail when the aforementioned SRUs are installed on a system.

* 4067433 (Tracking ID: 4067432)

SYMPTOM:
While upgrading to 7.4.2 Update 2 , VRTSvlic patch package fails to install.

DESCRIPTION:
VRTSvlic patch package has a package level dependency on VRTSpython. When upgrading the VRTSvlic patch package, only VRTSvlic publisher is set. VRTSvlic publisher fails to resolve the VRTSpython dependency and installation is unsuccessful.

RESOLUTION:
Installer checks if VRTSvlic and VRTSpython are in the patch list. If both are present, installer sets the publisher for VRTSvlic and VRTSpython before running the command to install the VRTSvlic patch. The package level dependency is thus resolved and VRTSvlic and VRTSpython patches get installed.

* 4070908 (Tracking ID: 4071690)

SYMPTOM:
The InfoScale product installer prompts you to enter the host name or the IP address and the port number of an edge server.

DESCRIPTION:
If the edge server details not provided, the InfoScale server is not registered with the edge server. Consequently, the installer does not perform InfoScale configurations on the InfoScale server.

RESOLUTION:
The installer is updated to perform Infoscale configurations without registering the Infoscale server to an edge server. It no longer prompts you for the edge server details.

* 4079500 (Tracking ID: 4079853)

SYMPTOM:
Patch installer flashes a false error message with -precheck option.

DESCRIPTION:
while installing patch with -precheck option installer flashes a false error message - 'CPI ERROR V-9-0-0 A more recent version of InfoScale Enterprise, 7.4.2.1100, is already installed on server'.

RESOLUTION:
A check added for hotfixupgrade and precheck both for performing further task.

* 4079916 (Tracking ID: 4079922)

SYMPTOM:
The product installer fails to complete the installation after it automatically downloads a required support patch from SORT that contains a VRTSperl package. The following error is logged:
CPI ERROR V-9-0-0
0 No pkg object defined for pkg VRTSperl530 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 VRTSperl 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 VRTSperl package on a system.

* 4080100 (Tracking ID: 4080098)

SYMPTOM:
Installer fails to complete the CP server configuration. The following error is logged:
CPI ERROR V-9-40-4422 Unable to create CA certificate /var/VRTScps/security/certs/ca.crt on <<system>>
CPI ERROR V-9-40-4427 Unable to create csr file /var/VRTSvxfen/security/certs/client_{<<uuid>>}.csr for <<system>> on <<system>>

DESCRIPTION:
Installer uses the 'openssl req' command to create CA certificate and csr file. With VRTSperl 5.34.0.2 onwards, openssl version is updated. The updated version requires config file to be passed with the 'openssl req' command by using -config paramater. Consequently, the installer fails to create CA certificate and csr file causing CP server configuration failure.

RESOLUTION:
Product installer is updated to pass the configuration file with the 'openssl req' command only.

* 4081964 (Tracking ID: 4081963)

SYMPTOM:
VRTSvxfs patch fails to install on Linux platforms while applying the security patch for 742 SP1.

DESCRIPTION:
VRTSvxfs patch needs veki module to be loaded before it loads its modules. VRTSvxfs patch rpm verifies whether Veki module is loaded. If it is not loaded, VRTSvxfs patch does not get installed and an error message appears.

RESOLUTION:
A new preinstall check added to the CPI installer for VRTSvxfs to verify whether veki is loaded, and loads it before VRTSvxfs patch is applied.

* 4084977 (Tracking ID: 4084975)

SYMPTOM:
Installer fails to complete the CP server configuration. The following error is logged:
CPI ERROR V-9-40-4422 Unable to create CA certificate /var/VRTScps/security/certs/ca.crt on <<system>>
CPI ERROR V-9-40-4427 Unable to create csr file /var/VRTSvxfen/security/certs/client_{<<uuid>>}.csr for <<system>> on <<system>>

DESCRIPTION:
To create CA certificate and csr file, installer uses the 'openssl req' command and passes the openssl configuration file '/opt/VRTSperl/non-perl-libs/bin/openssl.cnf' by using -config parameter to the 'openssl req' command. OpenSSL version 1.0.2, does not have an openssl configuration file. Hence, the installer fails to create CA certificate and csr file, and CP server configuration fails.

RESOLUTION:
Installer updated to check and pass the openssl configuration file only if the file is present on the system.

* 4085612 (Tracking ID: 4087319)

SYMPTOM:
Installer fails to uninstall VxVM while upgrading from 7.4.2 to 8.0U1.

DESCRIPTION:
While upgrading, uninstallation of previous rpms fails if the semodule is not loaded. Installer fails to uninstall VxVM if semodule is not loaded before uninstallation.

RESOLUTION:
Installer enhanced to check and take appropriate action if semodule vxvm is not loaded before uninstallation.

* 4086047 (Tracking ID: 4086045)

SYMPTOM:
When Infoscale cluster is reconfigured, LLT, GAB, VXFEN services fail to start after reboot.

DESCRIPTION:
Installer updates the /etc/sysconfig/<<service>> file and incorrectly sets START_<<service>> and STOP_<<service>> value as '0' in pre_configure task even when VCS is not set for reconfiguration. These services thus fail to start after reboot.

RESOLUTION:
Installer is enhanced to not to update the /etc/sysconfig/<<service>> files when VCS is not set for reconfiguration.

* 4086570 (Tracking ID: 4076583)

SYMPTOM:
On a Solaris system, the InfoScale installer runs set/unset publisher several times but does not disable 
the publisher. The deployment process slows down as a result.

DESCRIPTION:
CPI installer sets/unsets the Veritas publisher several times which slows the deployment process.

RESOLUTION:
The Installer sets all the publishers together. Subsequently the higher version of the package/patch available in the publishers 
is selected. Solaris and other publishers except Veritas are also disabled.

* 4086624 (Tracking ID: 4086623)

SYMPTOM:
Installer fails to complete the CP server configuration. The following error is logged:
CPI ERROR V-9-40-4422 Unable to create CA certificate /var/VRTScps/security/certs/ca.crt on <<system>>
CPI ERROR V-9-40-4427 Unable to create csr file /var/VRTSvxfen/security/certs/client_{<<uuid>>}.csr for <<system>> on <<system>>

DESCRIPTION:
Installer check the openssl_conf file on client nodes instead of CP server, consequently even if openssl_conf file is not present on CP server installer tries to utilize the same and fails to generate the CA certificate and csr files.

RESOLUTION:
Product installer is updated to check and pass the configuration file from CP server.

* 4087148 (Tracking ID: 4088698)

SYMPTOM:
CPI installer tries to download a must-have patch whose version is lower than the version specified in media path. If installer is unable to download, the following error message is displayed:
CPI ERROR V-9-30-1114 Failed to connect to SORT (https://sort.veritas.com), the patch <<patchname>> is required to deploy this product.

DESCRIPTION:
CPI installer tries to download a lower version must-have patch even if patch bundle(s) of equal or higher version of all the patches from the must-have patch is provided in the media path.

RESOLUTION:
CPI installer does not download the required must-have patch if equal or higher version patches are supplied in the mediapath.

* 4087809 (Tracking ID: 4086533)

SYMPTOM:
VRTSfsadv pkg fails to upgrade from 7.4.2 U4 to 8.0 U1 while using yum upgrade. Following error observed:
The fsdedupschd.service is running.  Please stop fsdedupschd.service before upgrading.
error: %prein(VRTSfsadv-8.0.0.1700-RHEL8.x86_64) scriptlet failed, exit status 1

DESCRIPTION:
fsdedupschd service is started as a post-installation task of VRTSfsadv 7.4.2.2600 Package. Before yum upgrade to 8.0 U1, installer does not set up the fsdedupschd service and  VRTSfsadv package fails to upgrade.

RESOLUTION:
Installer is enhanced to handle the start and stop of VRTSfsadv-related services i.e fsdedupschd and vxfs_replication.

* 4089657 (Tracking ID: 4089934)

SYMPTOM:
Installer does not update the '/opt/VRTSvcs/conf/config/types.cf' file after a VRTSvcs patch upgrade.

DESCRIPTION:
If '../conf/types.cf' file is changed with a VRTSvcs patch, during patch upgrade installer does not update the '..conf/config/types.cf' file. It needs to be updated  manually to avoid unexpected issues.

RESOLUTION:
Product installer is enhanced to correctly populate the '..conf/config/types.cf' file if '../conf/types.cf' file is changed with a VRTSvcs patch.

* 4089815 (Tracking ID: 4089867)

SYMPTOM:
On Linux, Installer fails to start the fsdedupschd service if VRTSfsadv 7.4.2.0000 is installed on the system.

DESCRIPTION:
VRTSfsadv 7.4.2.0000 doesn't have systemctl wrapper for fsdedupschd start script and there is missing shebang line in the bash script. Because of two issues, installer fails to start the fsdedupschd service.

RESOLUTION:
Installer is enhanced to handle the start and stop of VRTSfsadv-related services i.e fsdedupschd and vxfs_replication only if VRTSfsadv 7.4.2.2600 or higher is installed.

* 4092407 (Tracking ID: 4092408)

SYMPTOM:
CPI installer fails to correctly identify status of vxfs_replication service.

DESCRIPTION:
Installer parses 'ps -ef' output to determine if vxfs_replication service has started. Because of an intermediate 'pidof' process, installer incorrectly identifies status of vxfs_replication service as started and during poststart check fails, as vxfs_replication had not started.

RESOLUTION:
Product installer is updated to skip the 'pidof' process while determining the vxfs_replication service status.

* 4100693 (Tracking ID: 4076583)

SYMPTOM:
On a Solaris system, the InfoScale installer runs set/unset publisher several times but does not disable 
the publisher. The deployment process slows down as a result.

DESCRIPTION:
CPI installer sets/unsets the Veritas publisher several times which slows the deployment process.

RESOLUTION:
The Installer sets all the publishers together. Subsequently the higher version of the package/patch available in the publishers 
is selected. Solaris and other publishers except Veritas are also disabled.



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


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


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


OTHERS
------
NONE