Translation Notice
Please note that this content includes text that has been machine-translated from English. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.
cpi-Patch-7.3.1.1700
Patch
Abstract
This patch resolves multiple issues. Please go through README document for details.
Description
Sort ID: 16042
Incidents: 3944164,3945461,3948728,3949312,3950586,3950736,3953503,3957571,3965605,3969114,3972659,3980564,3981912,3995210,3995522,3996283,3998396,4012741
Patch ID: None
* * * READ ME * * * * * * CPI 7.3.1 * * * * * * Patch 1700 * * * Patch Date: 2020-09-08 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.3.1 Patch 1700 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 Solaris 12 SPARC BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * InfoScale Availability 7.3.1 * InfoScale Enterprise 7.3.1 * InfoScale Foundation 7.3.1 * InfoScale Storage 7.3.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 7.3.1.1700 * 3944164 (3944161) Installer could not upgrade VRTSvxfs and VRTSodm inside non-global zones * 3945461 (3945456) When performing an upgrade from InfoScale 7.3 to 7.3.1.xxx, CPI installs the packages from the 7.3.1.xxx patch only and does not install the base packages of 7.3.1 GA. * 3948728 (3948729) InfoScale 7.3.1 installation fails if the CPI installer auto downloads the applicable OS update patches that are available on SORT * 3949312 (3949310) After applying VxVM 7.3.1.100 patch on Solaris, GAB service fails to auto-start on reboot. * 3950586 (3950589) On Solaris 11, installation or upgrade of InfoScale to version 7.3.1 fails with an error. * 3950736 (3950762) Configuration of LLT over TCP fails if you configure LLT while installing InfoScale 7.3.1 using CPI, or if the cluster nodes have inconsistent interface names (tags). * 3953503 (3953507) The "-version" option of InfoScale 7.3.1 installer fails to download the available Maintenance or Patch releases * 3957571 (3957572) InfoScale 7.3.1 installer does not stop the veki process while performing the installer -stop operation * 3965605 (3965602) Rolling upgrade Phase2 fails if a patch is installed as a part of Rolling upgrade Phase1. * 3969114 (3969113) The 'pkg list <pkg name>' command to check the uucp and bourne package fail for solaris 11.4 and later versions * 3972659 (3972657) Veki fails to unload during patch installation when -patch_path option is used with the installer. * 3980564 (3980562) CPI does not perform the installation when two InfoScale patch paths are provided, and displays the following message: "CPI ERROR V-9-30-1421 The patch_path and patch2_path patches are both for the same package: VRTSinfoscale". * 3981912 (3982197) When a system restarts after an InfoScale 7.3.1 patch installation, some of the processes may fail to start. * 3995210 (3995207) The installer fails to install the 'infoscale-sles12.4_x86_64-Patch-7.3.1.1100' patch on SLES 12 SP4. * 3995522 (3959540) The installer fails to validate the Oracle Clusterware/Grid Infrastructure Home directory for Oracle 18C and later versions * 3996283 (3996282) The installer script fails to stop the vxfen service while configuring InfoScale components or applying patches. * 3998396 (3998395) The addnode operation fails during symmetry check of a new node with other nodes in the cluster. * 4012741 (4012985) Installer fails to complete installation after it automatically downloads a required support patch from SORT that contains a VRTSpython package. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following incidents: Patch ID: 7.3.1.1700 * 3944164 (Tracking ID: 3944161) 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. * 3945461 (Tracking ID: 3945456) SYMPTOM: CPI assumes that the third digit in an InfoScale 7.3.1 version indicates a patch release, and not a GA release. It then upgrades the packages from the patch only and does not upgrade the base packages. DESCRIPTION: To compare release versions and set the type of installation, CPI compares the currently installed release version with the target release version to be installed. However, instead of considering all the digits in a release version, it incorrectly compares only the first two digits. In this case, CPI compares 7.3 with 7.3.1, and finds that the first 2 digits match exactly. Thus, it assumes that the base release is already installed and so it only installs the patch packages. RESOLUTION: This hotfix updates the CPI to recognize InfoScale 7.3.1 as a higher release and 7.3.1.100 (for example) as a patch release. CPI can now properly upgrade the base packages first and then proceed to upgrade the packages that are in the patch. * 3948728 (Tracking ID: 3948729) SYMPTOM: InfoScale 7.3.1 installation fails if the CPI installer auto downloads the applicable OS update patches that are available on SORT DESCRIPTION: During the product installation, using CPI, the installer auto checks for the available OS update patches on SORT, and then downloads them. In case of patch auto download, the installer fails to proceed with the installation because it fails to correctly identify the product package base version. RESOLUTION: This hotfix modifies the installer behavior to correctly identify the product package base version. * 3949312 (Tracking ID: 3949310) SYMPTOM: After applying the VxVM patch 7.3.1.100, GAB service fails to auto-start on reboot. DESCRIPTION: After applying the VxVM patch 7.3.1.100, the service GAB gets removed from system's service auto-start list. Due to this, the GAB service fails to start upon system reboot. RESOLUTION: This hotfix enables the installer to make sure that the GAB service is added back into system's service startup list, so that it gets loaded automatically after the system is rebooted. The installer is updated to check for entries in system's service auto-start list and add the service if its not already available. * 3950586 (Tracking ID: 3950589) SYMPTOM: On Solaris 11, installation or upgrade of InfoScale to version 7.3.1 fails with the following error: "Can't use an undefined value as an ARRAY reference" DESCRIPTION: While installing InfoScale 7.3.1 or upgrading to 7.3.1 On Solaris 11, a CPI patch is auto-downloaded from SORT. This patch was provided to solve the issue in handling VRTSodm and VRTSvxfs packages in non-global zone. As this patch is set to initiate the array only if odm is present in non-global zones, the array does not get initiated on the machines where odm is NOT present in non-global zones and displays this error. RESOLUTION: The CPI code is modified to initiate the array by default for all the cases and to prevent undefined value errors for the array reference. * 3950736 (Tracking ID: 3950762) SYMPTOM: while installing InfoScale 7.3.1 using CPI, you may observe that: Even if you choose to configure LLT over TCP, the installer always configures LLT over UDP. If the cluster nodes have inconsistent interface names(tags)in the configuration file (llttab), LLT over TCP and UDP configurations fail. DESCRIPTION: Configuration of LLT over TCP fails if you configure LLT while installing InfoScale 7.3.1 using CPI. This happens because of the following reasons: The CPI code has hardcoded linktype value set to 'udp' that prohibits CPI from configuring LLT over 'tcp'. While configuring LLT over UDP or TCP through CPI, the installer creates the configuration file (llttab) and adds the interface names to it. For these interface names, the installer uses the local NIC identifiers referring to remote IP addresses. This may cause inconsistencies in the defined interface names. For example: Node1 has eth0 - 192.168.180.1 (eth2 doesn't exist) Node2 has eth2 - 192.168.180.2 (eth0 doesn't exist) To deal with such inconsistent NIC identifiers across nodes, llttab for Node1 should use its local NICs (i.e. eth0) while configuring set-addr option for Node2 and vice versa. RESOLUTION: This hotfix enables the installer to: Configure LLT over TCP as well as UDP. Handle inconsistent interface names across nodes in the cluster. * 3953503 (Tracking ID: 3953507) SYMPTOM: The "-version" option of InfoScale 7.3.1 installer fails to download the available Maintenance or Patch releases DESCRIPTION: The "-version" option of installer lets you view the currently installed InfoScale version, and to download the available Maintenance or Patch releases. However, InfoScale 7.3.1 installer is unable the get the path of the repository where the Maintenance or Patch releases should be downloaded. RESOLUTION: The installer code is modified to either use /OPT/VRTS/repository as the default repository or to accept a different location to download the suggested releases. * 3957571 (Tracking ID: 3957572) SYMPTOM: InfoScale 7.3.1 installer does not stop the veki process while performing the installer -stop operation DESCRIPTION: The veki module remains loaded on the node even after performing the installer -stop operation. This happens because the InfoScale 7.3.1 installer fails to include the veki process in the stop processes list. RESOLUTION: The installer is enhanced to stop the veki process during the installer -stop operation. * 3965605 (Tracking ID: 3965602) SYMPTOM: When a patch is installed as a part of rolling upgrade Phase1, the rolling upgrade Phase2 fails with the error: A more recent version of InfoScale Enterprise, 7.3.1.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 Phase2 with the error: A more recent version of InfoScale Enterprise, 7.3.1.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. * 3969114 (Tracking ID: 3969113) SYMPTOM: The 'pkg list <pkg name>' command to check the uucp and bourne package fail for solaris 11.4 and later versions DESCRIPTION: In Solaris 11.4 or later, the /usr/sunos/bin/sh file is part of the bourne package and the /var/spool/locks directory is part of the uucp package. For the prior Solaris releases, this file and directory were included in the core-os package. As these files are no longer available in the core-os package, the 'pkg list <pkg name>' command to check the uucp and bourne package fail for solaris 11.4 and later versions. RESOLUTION: The installer is enhanced to use the 'pkg search -l <file or directory>' command to identify if the file or directory is available in the installed packages. If it is not available, the installer prompts the user to install the required packages(uucp/bourne). For the versions prior to Solaris 11.4, the core-os package is available and the installer continues without failing. * 3972659 (Tracking ID: 3972657) SYMPTOM: When the -patch_path option is used, the installer fails to install the VRTSveki patch. DESCRIPTION: When the VRTSveki patch is present in a patch bundle, if the GA installer is run with the -patch_path option, it fails to install the VRTSveki patch. Consequently, the installation of any dependent VxVM patches also fails. This issue occurs because the veki module, and any other modules that depend on it, are loaded immediately after the packages are installed. When a patch installation starts, the Veki patch attempts to unload the veki module, but fails, because the dependent modules have a hold on it. RESOLUTION: This hotfix updates CPI so that if the -patch_path option is used when a VRTSveki patch is present in the bundle, it first unloads the dependent modules and then unloads the veki module. * 3980564 (Tracking ID: 3980562) SYMPTOM: CPI does not perform the installation when two InfoScale patch paths are provided, and displays the following message: "CPI ERROR V-9-30-1421 The patch_path and patch2_path patches are both for the same package: VRTSinfoscale". DESCRIPTION: CPI checks whether the patches mentioned with the patch_path option are the same. Even though the patch bundles are different, they have the same starting string, VRTSinfoscale, followed by the version number. CPI does not compare the version part of the patch bundle name, and so it incorrectly assumes them to be the same. Therefore, CPI does not install the patch bundles simultaneously, and instead, displays the inappropriate error. RESOLUTION: CPI is updated to check the complete patch bundle name including the version, for example: VRTSinfoscale740P1100. Now, CPI can properly differentiate between the patches and begin the installation without displaying the inappropriate error. * 3981912 (Tracking ID: 3982197) SYMPTOM: When a system restarts after an InfoScale 7.3.1 patch installation, some of the processes may fail to start. DESCRIPTION: During a patch installation on InfoScale 7.3.1, the installer first comments out all forceload entries in the /etc/system file and then proceeds with the installation. After the installation is complete, the installer uncomments the forceload entries. However, if any of the vxio, vxspec, or vxdmp processes are already running, the installer does not uncomment the corresponding forceload entries. Therefore, when the system restarts, the dependent processes that are listed in the /etc/system file fail to start. RESOLUTION: This CPI patch enables the installer to forcefully check the content of /etc/system, and process the forceload entries even if any of the vxio, vxspec, or vxdmp processes are running. * 3995210 (Tracking ID: 3995207) SYMPTOM: The installer fails to install the 'infoscale-sles12.4_x86_64-Patch-7.3.1.1100' patch on SLES 12 SP4. DESCRIPTION: InfoScale support for SUSE Linux Enterprise Server 12 SP4 is introduced with the 'infoscale-sles12.4_x86_64-Patch-7.3.1.1100' patch. However, the path of the 'ethtool' command is changed in SLES 12 SP4. Therefore, the installer does not recognize the changed path and fails to install. The following error is logged: CPI ERROR V-9-30-1570 The following required OS commands are missing on <<node name>>: /bin/ls: cannot access '/sbin/ethtool': No such file or directory RESOLUTION: The path of the 'ethtool' command is updated in the installer for SLES12 SP4. * 3995522 (Tracking ID: 3959540) SYMPTOM: The installer fails to validate the Oracle Clusterware/Grid Infrastructure Home directory for Oracle 18C and later versions DESCRIPTION: During the Relink Oracle Database Binary operation, the installer uses the crs_stat command to fetch the status information for resource on the cluster node. However, the crs_stat command is deprecated after Oracle 12 release. Therefore, for Oracle 18C and later versions, the installer cannot validate the Grid home directory and fails. RESOLUTION: The common product installer is enhanced to dynamically choose whether to use the crs_stat command or the upgraded crs_ctl command to validate the Grid home directory for Oracle Grid Infrastructure. * 3996283 (Tracking ID: 3996282) SYMPTOM: The installer script fails to stop the vxfen service while configuring InfoScale components or applying patches. DESCRIPTION: When InfoScale Enterprise is installed using the CPI, the value of the START_<<COMP>> and the STOP_<<COMP>> variables is set to '1' in the configuration files for some components like vxfen, amf, and llt. During the post-installation phase, the CPI script sets these values back to '0'. When InfoScale Enterprise is installed using Yum or Red Hat Satellite, the values of these variables remain set to '1' even after the installation is completed. Later, if CPI is used to install patches or to configure any of the components on such an installation, the installer script fails to stop the vxfen service. RESOLUTION: To avoid such issues, the installer script is updated to check the values of the START_<<COMP>> and the STOP_<<COMP>> variables and set them to '0' during the pre-configuration phase. * 3998396 (Tracking ID: 3998395) SYMPTOM: For InfoScale 7.3.1 Patch 2300 onwards, the addnode operation fails with the following error message: "Cluster protocol version mismatch was detected between cluster <<cluster_name>> and <<new node name>>. Refer to the Configuration and Upgrade Guide for more details on how to set or upgrade cluster protocol version." DESCRIPTION: In InfoScale 7.3.1 Patch 2300 the cluster protocol version was changed from 190 to 200 in the VxVM component. However, the same update is not made in the installer, which continues to set the default cluster protocol version to 190. During the addnode operation, when the new node is compared with the other cluster nodes, the cluster protocol versions do not match, and the error is displayed. RESOLUTION: The common product installer is enhanced to check the installed VRTSvxvm package version on the new node and accordingly set the cluster protocol version. * 4012741 (Tracking ID: 4012985) SYMPTOM: The product installer fails to complete the installation after it automatically downloads a required support patch from SORT that contains a VRTSpython package. The following error is logged: CPI ERROR V-9-0-0 0 No pkg object defined for pkg VRTSpython351 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 VRTSpython 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 VRTSpython package on a system. INSTALLING THE PATCH -------------------- 1. Copy the hot-fix CPI_7.3.1_P17.pl to /tmp 2. Run installation scripts with the hot-fix Example: ./installer -require /tmp/CPI_7.3.1_P17.pl REMOVING THE PATCH ------------------ NONE SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE
Applies to the following product releases
Update files
|
File name | Description | Version | Platform | Size |
---|