* * * READ ME * * * * * * CPI 7.4.1 * * * * * * Patch 1200 * * * Patch Date: 2019-11-07 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.1 Patch 1200 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- AIX RHEL6 x86-64 RHEL7 x86-64 SLES11 x86-64 SLES12 x86-64 SLES15 x86-64 Solaris 11 SPARC Solaris 11 X86 BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * InfoScale Availability 7.4.1 * InfoScale Enterprise 7.4.1 * InfoScale Foundation 7.4.1 * InfoScale Storage 7.4.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 7.4.1.1200 * 3969748 (3969438) Rolling upgrade fails when local node is specified at the system name prompt on non-fss environment. * 3970852 (3970848) The CPI configures the product even if you use the -install option while installing the InfoScale Foundation version 7.x or later. * 3972077 (3972075) Veki fails to unload during patch installation when -patch_path option is used with the installer. * 3973119 (3973114) While upgrading to Infoscale 7.4, the installer fails to stop vxspec, vxio and vxdmp as vxcloudd is still running. * 3979596 (3979603) While upgrading from InfoScale 7.4.1 to 7.4.1.xxx, CPI installs the packages from the 7.4.1.xxx patch only and not the base packages of 7.4.1 GA. * 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". * 3980944 (3981519) An uninstallation of InfoScale 7.4.1 using response files fails with an error. * 3985584 (3985583) The addnode operation fails during symmetry check of a new node with other nodes in the cluster. * 3986468 (3987894) An InfoScale 7.4.1 installation fails even though the installer automatically downloads the appropriate platform support patch from SORT. * 3986572 (3965602) Rolling upgrade Phase2 fails if a patch is installed as a part of Rolling upgrade Phase1. * 3986960 (3986959) The installer fails to install the 'infoscale-sles12.4_x86_64-Patch-7.4.1.100' patch on SLES 12 SP4. * 3987228 (3987171) The installer takes longer than expected time to start installation process. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following incidents: Patch ID: 7.4.1.1200 * 3969748 (Tracking ID: 3969438) SYMPTOM: Rolling upgrade fails with the error: CPI ERROR V-9-0-0 0 Cannot execute _cmd_vxdg list | _cmd_grep enabled | _cmd_awk '{print $1}' on system_name with undefined sys->{padv} DESCRIPTION: The following prompt appears as part of the rolling upgrade process: Enter the system name of the cluster on which you would like to perform rolling upgrade [q,?] After the prompt, the installer suggests the names of systems on which to perform the upgrade. You may select one of the suggested system names, or you may type a system name, and then press Enter. Either way, if you specify the system name of the local node, the installer displays the following error and exits. CPI ERROR V-9-0-0 0 Cannot execute _cmd_vxdg list | _cmd_grep enabled | _cmd_awk '{print $1}' on system_name with undefined sys->{padv} RESOLUTION: The installer is enhanced to verify if the fss disk group is available. This enhancements was made for the Linux, Solaris, and Aix platforms. * 3970852 (Tracking ID: 3970848) SYMPTOM: The CPI configures the product even if you use the -install option while installing the InfoScale Foundation version 7.x or later. DESCRIPTION: When you use the CPI to install InfoScale Foundation, the ./installer option performs the installation and configurations by default. If you use the -install option, the installer must only install the packages and not perform the configuration. However, in case of InfoScale Foundation version 7.x or later, when you use the -install option, the installer continues to configure the product after installation. RESOLUTION: For InfoScale Foundation, the CPI is modified so that the -install option only install the packages. Users can then use the -configure option to configure the product. * 3972077 (Tracking ID: 3972075) 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. * 3973119 (Tracking ID: 3973114) SYMPTOM: While upgrading Infoscale 7.4, the installer fails to stop vxspec, vxio and vxdmp as vxcloudd is still running. DESCRIPTION: As the vxcloudd is running it fails to stop vxspec, vxio and vxdmp. RESOLUTION: Modified the CPI code to stop vxcloudd before stopping vxspec, vxio and vxdmp. * 3979596 (Tracking ID: 3979603) SYMPTOM: CPI assumes that the third digit in an InfoScale 7.4.1 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.1.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.1 as a base version and 7.4.1.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. * 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. * 3980944 (Tracking ID: 3981519) SYMPTOM: An uninstallation of InfoScale 7.4.1 using response files fails with an error: CPI ERROR V-9-40-1582 Following edge server related entries are missing in response file. Please correct. edgeserver_host edgeserver_port DESCRIPTION: When you uninstall InfoScale using a response file, the installer checks whether the response file contains the edge server related entries. If these entries are not available in the response file, the uninstall operation fails with the following error: CPI ERROR V-9-40-1582 Following edge server related entries are missing in response file. Please correct. edgeserver_host edgeserver_port This issue occurs because the installer checks the availability of these entries in the response file while performing any operations using the response files. However, these entries are required only for the configure and upgrade operations. RESOLUTION: The installer is enhanced to check the availability of the edge server related entries in the response file only for the configure or upgrade operations. * 3985584 (Tracking ID: 3985583) SYMPTOM: For InfoScale 7.4.1 Patch 1200 onwards, the addnode operation fails with the following error message: "Cluster protocol version mismatch was detected between cluster <> and <>. Refer to the Configuration and Upgrade Guide for more details on how to set or upgrade cluster protocol version." DESCRIPTION: In InfoScale 7.4.1 Patch 1200 the cluster protocol version was changed from 220 to 230 in the VxVM component. However, the same update is not made in the installer, which continues to set the default cluster protocol version to 220. 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. * 3986468 (Tracking ID: 3987894) SYMPTOM: An InfoScale 7.4.1 installation fails even though the installer automatically downloads the appropriate platform support patch from SORT. DESCRIPTION: During an InfoScale installation, the product installer looks for any applicable platform support patches that are available on SORT and automatically downloads them. Thereafter however, it fails to correctly identify the base version of the product package on the system, and hence fails to complete the installation even though the appropriate patch is available. RESOLUTION: The installer is updated to correctly identify the base version of the product package. * 3986572 (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. * 3986960 (Tracking ID: 3986959) SYMPTOM: The installer fails to install the 'infoscale-sles12.4_x86_64-Patch-7.4.1.100' 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.4.1.100' 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 <>: /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. * 3987228 (Tracking ID: 3987171) SYMPTOM: The installer takes longer than expected time to start installation process. DESCRIPTION: This issue occurs because, before it begins the installation, the installer incorrectly attempts to download latest CPI patches using a private IPv6 address until the process times out. RESOLUTION: The installer is updated to use first available public IP address to download latest CPI patches so that it can complete the activity and start the installation within the expected amount of time. INSTALLING THE PATCH -------------------- 1. Copy the hot-fix CPI_7.4.1_P12.pl to /tmp 2. Run installation scripts with the hot-fix Example: ./installer -require /tmp/CPI_7.4.1_P12.pl REMOVING THE PATCH ------------------ NONE SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE