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-8.0.2.2000
Patch
Abstract
This patch resolves multiple issues. Please check README document for further details.
Description
Sort ID:21983
Incidents:
4115603,4115707,4115874,4116368,4116406,4116879,4116995,4117956,4121961,4122442,4122749,4126470,4127111,4130377,
4131315,4131684,4132411,4133019,4133469,4135015,4136211,4139609,4140512,4157440,4157696,4158650,4159940,4161937,
4164945,4165118,4165727,4165730,4165840,4166659,4166980,4167308,4176027,4177618,4178007,4181039,4181282,4181787,
4184438,4187076,4187880,4187965,4188727,4189009,4189118
Patch ID: None
* * * READ ME * * *
* * * CPI 8.0.2 * * *
* * * Patch 2000 * * *
Patch Date: 2025-04-03
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 8.0.2 Patch 2000
OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
AIX
RHEL7 x86-64
RHEL8 x86-64
RHEL9 x86-64
SLES12 x86-64
SLES15 x86-64
Solaris 11 SPARC
Solaris 11 X86
BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
* InfoScale Availability 8.0.2
* InfoScale Enterprise 8.0.2
* InfoScale Foundation 8.0.2
* InfoScale Storage 8.0.2
SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 8.0.2.2000
* 4115603 (4115601) On Solaris, Publisher list gets displayed during Infoscale start,stop, and uninstall process and does not display a
unique publisher list during install and upgrade.
* 4115707 (4126025) While performing full upgrade of the secondary site, SRL missing & RLINK dissociated error observed.
* 4115874 (4124871) Configuration of Vxfen fails for a three-node cluster on VMs in different AZs
* 4116368 (4123645) During the Rolling upgrade response file creation, CPI is asking to unmount the VxFS filesystem.
* 4116406 (4123654) Removed unnecessary swap space message.
* 4116879 (4126018) During addnode, installer fails to mount resources.
* 4116995 (4123657) Installer retries upgrading protocol version post-upgrade.
* 4117956 (4104627) Providing multiple-patch support up to 10 patches.
* 4121961 (4123908) Installer does not register InfoScale hosts to the VIOM Management Server after InfoScale configuration.
* 4122442 (4122441) CPI is displaying licensing information after starting the product through the response file.
* 4122749 (4122748) On Linux, had service fails to start during rolling upgrade from InfoScale 7.4.1 or lower to higher InfoScale version.
* 4126470 (4130003) Installer failed to start vxfs_replication while performing Configuration of Enterprise on OEL 9.2
* 4127111 (4127117) On a Linux system, you can configure the GCO(Global Cluster option) with a hostname by using InfoScale installer.
* 4130377 (4131703) Installer performs dmp include/exclude operations if /etc/vx/vxvm.exclude is present on the system.
* 4131315 (4131314) Environment="VCS_ENABLE_PUBSEC_LOG=0" is added from cpi in install section of service file instead of Service section.
* 4131684 (4131682) On SunOS, installer prompts the user to install 'bourne' package if it is not available.
* 4132411 (4139946) Rolling upgrade fails if the recommended upgrade path is not followed.
* 4133019 (4135602) Installer failed to update main.cf file with VCS user during reconfiguring a secured cluster to non-secured cluster.
* 4133469 (4136432) add node to higher version of infoscale node fails.
* 4135015 (4135014) CPI installer should not ask for install InfoScale after "./installer -precheck" is done.
* 4136211 (4139940) Installer failed to get the package version and failed due to PADV missmatch.
* 4139609 (4142877) Missing HF list not displayed during upgrade by using the patch release.
* 4140512 (4140542) Rolling upgrade failed for the patch installer
* 4157440 (4158841) VRTSrest verison changes support.
* 4157696 (4157695) In IS 7.4.2 U7 to IS 8.0.2 upgradation, VRTSpython version upgradation fails.
* 4158650 (4164760) The installer will check for dvd pkg version with the available patch pkg version to install the latest pkgs.
* 4159940 (4159942) The installer will not update existing file permissions.
* 4161937 (4160983) In Solaris, the vxfs modules are getting removed from current BE while upgrading the Infoscale to ABE.
* 4164945 (4164958) The installer will check for pkg version to allow EO tunable changes in config files.
* 4165118 (4171259) The installer will add the new node in cluster.
* 4165727 (4165726) Getting error message like "A more recent version of InfoScale Availability, 8.0.2.*, is already installed" when user tries to upgrade the patch on GA using RU and when user tries to upgrade the product from InfoScale Availability to InfoScale Enterprise.
* 4165730 (4165726) Getting error message like "A more recent version of InfoScale Availability, 8.0.2.*, is already installed" when user tries to upgrade the patch on GA using RU and when user tries to upgrade the product from InfoScale Availability to InfoScale Enterprise.
* 4165840 (4165833) InfoScale installer does not support installation using IPS repository on Solaris.
* 4166659 (4171256) The installer will ease in checking rvg role while the upgrading VVR host.
* 4166980 (4166979) [VCS] - VMwareDisks agent is unable to start and run after upgrade to RHEL 8.10 and Infoscale 8.0.2.1700
* 4167308 (4171253) IS 8.0.2U3 : CPI doesn't ask to set EO tunable in case of Infoscale upgrade
* 4176027 (4187081) The installer will now try to stop services forcefully if not stopped by sysctl command.
* 4177618 (4184454) We are changing code by adding dbed related checks
* 4178007 (4177807) We are changing message for CPC fencing not writing in env file /etc/vxenviron file
* 4181039 (4181037) We are making the etc/vx/vxdbed/dbedenv file accessible
* 4181282 (4181279) Configuration fails if dbed is not installed.
* 4181787 (4181786) VCS configuration with responsefile changing the interface bootproto from dhcp to none when we configure the LLT over UDP.
* 4184438 (4186642) The installer will not ask for VIOM registration in case of start option.
* 4187076 (4187074) The installer failed to go back after giving input to the EO permission question.
* 4187880 (4188117) The installer will now check for nmcom service for vvr startup status.
* 4187965 (4187964) The installer can now configure the cluster with a single nic.
* 4188727 (4188728) The installer can now configure the cluster existing vcs configuration files using the option -old_config during a fresh installation.
* 4189009 (4189008) LVM filesystem error on AIX.
* 4189118 (4189117) Adding "chkconfig" rpm as prerequisite in CPI installer.
DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following incidents:
Patch ID: 8.0.2.2000
* 4115603 (Tracking ID: 4115601)
SYMPTOM:
On Solaris, Publisher list gets displayed during Infoscale start,stop, and uninstall process and does not display a
unique publisher list during install and upgrade. A publisher list gets displayed during install and upgrade which is not unique.
DESCRIPTION:
On Solaris, Publisher list gets displayed during Infoscale start,stop, and uninstall process and does not display a
unique publisher list during install and upgrade. A publisher list gets displayed during install and upgrade which is not unique.
RESOLUTION:
Installer code modified to skip the publisher list during start, stop and uninstall process and get unique publisher list during install and upgrade.
* 4115707 (Tracking ID: 4126025)
SYMPTOM:
While performing full upgrade of the secondary site, SRL missing & RLINK dissociated error observed.
DESCRIPTION:
While performing full upgrade of the secondary site, SRL missing & RLINK dissociated error observed.
SRL volume[s] is[are] in recovery state which leads to failure in associating srl vol with rvg.
RESOLUTION:
Installer code modified to wait for recovery tasks to complete on all volumes and then proceed with associating srl with rvg.
* 4115874 (Tracking ID: 4124871)
SYMPTOM:
Configuration of Vxfen fails for a three-node cluster on VMs in different AZs.
DESCRIPTION:
Configuration of Vxfen fails for a three-node cluster on VMs in different AZs
RESOLUTION:
Added set-strictsrc 0 tunable to the llttab file in the installer.
* 4116368 (Tracking ID: 4123645)
SYMPTOM:
During the Rolling upgrade response file creation, CPI is asking to unmount the VxFS filesystem.
DESCRIPTION:
During the Rolling upgrade response file creation, CPI is asking to unmount the VxFS filesystem.
RESOLUTION:
Installer code modified to exclude VxFS file system unmount process.
* 4116406 (Tracking ID: 4123654)
SYMPTOM:
The installer gives a null swap space message.
DESCRIPTION:
The installer gives a null swap space message, as the swap space requirement is not needed anymore.
RESOLUTION:
Installer code modified and removed swap space message.
* 4116879 (Tracking ID: 4126018)
SYMPTOM:
During addnode, installer fails to mount resources.
DESCRIPTION:
During addnode, installer fails to mount resources; as new node system was not added to child SG of resources.
RESOLUTION:
Installer code modified to add new node to all SGs.
* 4116995 (Tracking ID: 4123657)
SYMPTOM:
Installer while performing upgrade Cluster Protocol version not upgraded post Full Upgrade
DESCRIPTION:
Installer while performing full upgrade Cluster Protocol version not upgraded post Full Upgrade.
RESOLUTION:
Installer code modified to retry upgrade to complete Cluster Protocol version .
* 4117956 (Tracking ID: 4104627)
SYMPTOM:
The installer supports maximum of 5 patches. The user is not able to provide more than 5 patches for installation.
DESCRIPTION:
The latest bundle package installer supports maximum 5 patches. The user is not able to provide more than 5 patches for installation.
RESOLUTION:
The installer code modified to support maximum of 10 patches for installation.
* 4121961 (Tracking ID: 4123908)
SYMPTOM:
Installer does not register InfoScale hosts to the VIOM Management Server after InfoScale configuration.
DESCRIPTION:
Installer does not register InfoScale hosts to the VIOM Management Server after InfoScale configuration.
RESOLUTION:
Installer is enhanced to register InfoScale hosts to VIOM Management Server by using both menu-driven program and responsefile. To register InfoScale hosts to VIOM Management Server by using responsefile, $CFG{gendeploy_path} parameter must be used. The value for $CFG{gendeploy_path} is the absolute path of gendeploy script from the local node.
* 4122442 (Tracking ID: 4122441)
SYMPTOM:
When the product starts through the response file, installer displays keyless licensing information on screen.
DESCRIPTION:
When the product starts through the response file, installer displays keyless licensing information on screen.
RESOLUTION:
Licensing code modified to skip licensing information during the product start process.
* 4122749 (Tracking ID: 4122748)
SYMPTOM:
On Linux, had service fails to start during rolling upgrade from InfoScale 7.4.1 or lower to higher InfoScale version.
DESCRIPTION:
VCS protocol version was supported from InfoScale 7.4.2 onwards. During rolling upgrade process from 7.4.1 or lower to higher InfoScale version, due to wrong release matrix data, installer tries to perform single phase rolling upgrade instead of two-phase rolling upgrade and had service fails to start.
RESOLUTION:
Installer is enhanced to perform two-phase rolling upgrade if installed Infoscale version is 7.4.1 or older.
* 4126470 (Tracking ID: 4130003)
SYMPTOM:
Installer failed to start vxfs_replication while performing Configuration of Enterprise on OEL 9.2
DESCRIPTION:
Installer failed to start vxfs_replication while performing Configuration of Enterprise on OEL 9.2
RESOLUTION:
Installer code modified to retry start vxfs_replication while Configuration of Enterprise.
* 4127111 (Tracking ID: 4127117)
SYMPTOM:
On a Linux system, the InfoScale installer configures the GCO(Global Cluster option) only with a virtual IP address.
DESCRIPTION:
On a Linux system, you can configure the GCO(Global Cluster option) with a hostname by using InfoScale installer on a
different cloud platform.
RESOLUTION:
Installer prompts for the hostname to configure the GCO.
* 4130377 (Tracking ID: 4131703)
SYMPTOM:
Installer performs dmp include/exclude operations if /etc/vx/vxvm.exclude is present on the system.
DESCRIPTION:
Installer performs dmp include/exclude operations if /etc/vx/vxvm.exclude is present on the system which is not required.
RESOLUTION:
Removed unnecessary dmp include/exclude operations which are launched after starting services in the container environment.
* 4131315 (Tracking ID: 4131314)
SYMPTOM:
Environment="VCS_ENABLE_PUBSEC_LOG=0" is added from cpi in install section of service file instead of Service section.
DESCRIPTION:
Environment="VCS_ENABLE_PUBSEC_LOG=0" is added from cpi in install section of service file instead of Service section.
RESOLUTION:
Environment="VCS_ENABLE_PUBSEC_LOG=0" is added in Service section of service file.
* 4131684 (Tracking ID: 4131682)
SYMPTOM:
On SunOS, installer prompts the user to install 'bourne' package if it is not available.
DESCRIPTION:
Installer had a dependency on 'usr/sunos/bin/sh', which is from 'bourne' package. 'bourne' package is deprecated with latest SRUs.
RESOLUTION:
Installer code is updated to use '/usr/bin/sh' instead of 'usr/sunos/bin/sh' thus removing bourne package dependency.
* 4132411 (Tracking ID: 4139946)
SYMPTOM:
Rolling upgrade fails if the recommended upgrade path is not followed.
DESCRIPTION:
Rolling upgrade fails if the recommended upgrade path is not followed.
RESOLUTION:
Installer code fixed to resolve rolling upgrade issues if recommended upgrade path is not followed.
* 4133019 (Tracking ID: 4135602)
SYMPTOM:
Installer failed to update main.cf file with VCS user during reconfiguring a secured cluster to non-secured cluster.
DESCRIPTION:
Installer failed to update main.cf file with VCS user during reconfiguring a secured cluster to non-secured cluster.
RESOLUTION:
Installer code checks are modified to update VCS user in main.cf file during reconfiguration of cluster from secured to non-secure.
* 4133469 (Tracking ID: 4136432)
SYMPTOM:
Installer failed to add node to a higher version of infoscale node.
DESCRIPTION:
Installer failed to add node to a higher version of infoscale node.
RESOLUTION:
Installer code modified to enable adding node to a higher version of infoscale node.
* 4135015 (Tracking ID: 4135014)
SYMPTOM:
CPI installer is asking "Would you like to install InfoScale" after "./installer -precheck" is done.
DESCRIPTION:
CPI installer is asking "Would you like to install InfoScale" after "./installer -precheck" is done. So it should not ask for installation after precheck is completed.
RESOLUTION:
Installer code modified to skip the question for installation after precheck is completed.
* 4136211 (Tracking ID: 4139940)
SYMPTOM:
Installer failed to get the package version and failed due to PADV missmatch.
DESCRIPTION:
Installer failed to get the package version and failed due to PADV missmatch.
RESOLUTION:
Installer code modified to retrieve proper package version.
* 4139609 (Tracking ID: 4142877)
SYMPTOM:
Missing HF list not displayed during upgrade by using the patch release.
DESCRIPTION:
Missing HF list not displayed during upgrade by using the patch release.
RESOLUTION:
Add prechecks in installer for identifying missing HFs and accept action from customer.
* 4140512 (Tracking ID: 4140542)
SYMPTOM:
Installer failed to rolling upgrade for patch
DESCRIPTION:
Rolling upgrade failed for the patch installer for the build version during mixed ru check
RESOLUTION:
Installer code modified to handle build version during mixed ru check.
* 4157440 (Tracking ID: 4158841)
SYMPTOM:
The installer supports VRTSrest version changes.
DESCRIPTION:
The installer now supports VRTSrest version changes.
RESOLUTION:
The installer code has been modified to enable the support for VRTSrest version changes.
* 4157696 (Tracking ID: 4157695)
SYMPTOM:
In IS 7.4.2 U7 to IS 8.0.2 upgradation, VRTSpython version upgradation fails.
DESCRIPTION:
In IS 7.4.2 U7 to IS 8.0.2 upgradation, VRTSpython version upgradation fails.
RESOLUTION:
Validation changes introduced for the VRTSpython package version.
* 4158650 (Tracking ID: 4164760)
SYMPTOM:
The installer is not checking dvd pkg version with the available patch pkg version
DESCRIPTION:
The installer is not checking dvd pkg version with the available patch pkg version due to that failed to install the latest pkgs.
RESOLUTION:
The installer code has been modified to check for dvd pkg version with the available patch pkg version to install the latest pkgs.
* 4159940 (Tracking ID: 4159942)
SYMPTOM:
The installer is used to update file permission.
DESCRIPTION:
The installer is used to update file permission.
RESOLUTION:
The installer code has been modified so that it will not update existing file permissions.
* 4161937 (Tracking ID: 4160983)
SYMPTOM:
In Solaris, after upgrading the Infoscale to ABE if we boot the current BE then the vxfs modules are not loading properly.
DESCRIPTION:
In Solaris, the vxfs modules are getting removed from current BE while upgrading the Infoscale to ABE.
RESOLUTION:
Installer code modified.
* 4164945 (Tracking ID: 4164958)
SYMPTOM:
The installer is making entries in the config files of EO tunable in the security patch.
DESCRIPTION:
The installer is not checking pkg version for the security patch, which is making entries in config files of EO tunables.
RESOLUTION:
The installer code has been modified to check pkg version for the security patch, which is making entries in config files of EO tunables.
* 4165118 (Tracking ID: 4171259)
SYMPTOM:
The installer is failing to add new node in cluster due to protocol version mismatch issue.
DESCRIPTION:
The installer is failing to add new node in cluster due to protocol version mismatch issue..
RESOLUTION:
The installer code has been modified to allow node to add in cluster.
* 4165727 (Tracking ID: 4165726)
SYMPTOM:
Getting error message like "A more recent version of InfoScale Availability, 8.0.2.*, is already installed" when user tries to upgrade the patch on GA using RU and when user tries to upgrade the product from InfoScale Availability to InfoScale Enterprise
DESCRIPTION:
Getting error message like "A more recent version of InfoScale Availability, 8.0.2.*, is already installed" when user tries to upgrade the patch on GA using RU and when user tries to upgrade the product from InfoScale Availability to InfoScale Enterprise
RESOLUTION:
Installer code modified.
* 4165730 (Tracking ID: 4165726)
SYMPTOM:
Getting error message like "A more recent version of InfoScale Availability, 8.0.2.*, is already installed" when user tries to upgrade the patch on GA using RU and when user tries to upgrade the product from InfoScale Availability to InfoScale Enterprise
DESCRIPTION:
Getting error message like "A more recent version of InfoScale Availability, 8.0.2.*, is already installed" when user tries to upgrade the patch on GA using RU and when user tries to upgrade the product from InfoScale Availability to InfoScale Enterprise
RESOLUTION:
Installer code modified.
* 4165840 (Tracking ID: 4165833)
SYMPTOM:
Unable to install InfoScale packages on Solaris using IPS repository.
DESCRIPTION:
InfoScale installer on Solaris did not support IPS repository-based installation. This feature has now been added to InfoScale on Solaris.
RESOLUTION:
InfoScale installer is modified to support IPS repository on Solaris.
Use the new option named "-ipsrepo" to define the IPS repository path or the repo name for performing IPS-based installation on Solaris.
* 4166659 (Tracking ID: 4171256)
SYMPTOM:
The installer is not allowing to upgrade primary rvg role vvr host to upgrade.
DESCRIPTION:
The installer is not allowing to upgrade primary rvg role vvr host to upgrade.
RESOLUTION:
The installer code has been modified to ease the checking vvr rvg role while upgrade.
* 4166980 (Tracking ID: 4166979)
SYMPTOM:
VMwareDisks agent is unable to start and run after upgrade
DESCRIPTION:
VMwareDisks agent is unable to start and run after upgrade
RESOLUTION:
Installer code modified.
* 4167308 (Tracking ID: 4171253)
SYMPTOM:
IS 8.0.2U3 : CPI doesn't ask to set EO tunable in case of Infoscale upgrade
DESCRIPTION:
InfoScale installer CPI doesn't ask to set EO tunable in case of Infoscale upgrade.
RESOLUTION:
InfoScale installer is modified.
* 4176027 (Tracking ID: 4187081)
SYMPTOM:
The installer failed to stop some services forcefully.
DESCRIPTION:
The installer failed to stop some services forcefully.
RESOLUTION:
The installer code has been modified to stop services forcefully.
* 4177618 (Tracking ID: 4184454)
SYMPTOM:
We are changing code by adding dbed related checks
DESCRIPTION:
We are changing code by adding dbed related checks
RESOLUTION:
Installer code modified
* 4178007 (Tracking ID: 4177807)
SYMPTOM:
We are changing message for CPC fencing not writing in env file /etc/vxenviron file
DESCRIPTION:
We are changing message for CPC fencing not writing in env file /etc/vxenviron file
RESOLUTION:
Installer code modified
* 4181039 (Tracking ID: 4181037)
SYMPTOM:
We are making the etc/vx/vxdbed/dbedenv file accessible
DESCRIPTION:
We are making the etc/vx/vxdbed/dbedenv file accessible
RESOLUTION:
Installer code modified
* 4181282 (Tracking ID: 4181279)
SYMPTOM:
User was trying to install rpm packages via yum.
After installation, configuring a cluster fails
DESCRIPTION:
User was trying to install rpm packages via yum.
After installation, configuring a cluster fails
RESOLUTION:
Installer code modified
* 4181787 (Tracking ID: 4181786)
SYMPTOM:
In network interface configuration file the interface method is changed to bootproto from dhcp, If we configure the the LLT over UDP.
DESCRIPTION:
If we use public interface(dhcp) interface for configuring LLT over UDP then as a result CPI changes the interface method to manual.
RESOLUTION:
Installer code modified
* 4184438 (Tracking ID: 4186642)
SYMPTOM:
The installer is asking VIOM registration question in case of start option.
DESCRIPTION:
The installer is asking VIOM registration question in case of start option.
RESOLUTION:
The installer code has been modified to not ask VIOM registration questions in case of start option.
* 4187076 (Tracking ID: 4187074)
SYMPTOM:
The installer failed to go back after giving input to the EO permission question.
DESCRIPTION:
The installer failed to go back after giving input to the EO permission question.
RESOLUTION:
The installer code has been modified to go back to EO permission question after input b (back).
* 4187880 (Tracking ID: 4188117)
SYMPTOM:
The installer failed to check status for vvr service.
DESCRIPTION:
The installer failed to start vvr service while startup.
RESOLUTION:
The installer code has been modified to check nmcom service for vvr startup status.
* 4187965 (Tracking ID: 4187964)
SYMPTOM:
The installer did not have support to configure the cluster with a single nic.
DESCRIPTION:
The installer did not have support to configure the cluster with a single nic.
RESOLUTION:
The installer code has been modified to configurthe the cluster with a single nic.
* 4188727 (Tracking ID: 4188728)
SYMPTOM:
The installer did not have support to configure the cluster with existing files on machines.
DESCRIPTION:
The installer did not support configuring the cluster with existing files on machines during a fresh installation.
RESOLUTION:
The installer code has been modified to configure the the cluster with existing files on machines.
* 4189009 (Tracking ID: 4189008)
SYMPTOM:
CPI - When CU is upgrading his stack from 7.4.2 to 8.0.2 he is getting CPI error that saying "Some LVM file systems are mounted on mount points /opt/splunk, /var/opt/zabbix on node1 and need to be unmounted before upgrade", So CU is unable to proceed with the upgrade.
DESCRIPTION:
When CU is upgrading his stack from 7.4.2 to 8.0.2 he is getting CPI error that saying "Some LVM file systems are mounted on mount points /opt/splunk, /var/opt/zabbix on node1 and need to be unmounted before upgrade", So CU is unable to proceed with the upgrade. Cu want to upgrade the stack without unmounting the LVM filesystem.
RESOLUTION:
Installer code modified.
* 4189118 (Tracking ID: 4189117)
SYMPTOM:
CPI - If "chkconfig" rpm not present on the node then CPI installer not showing it in the prerequisite list of rpm while intsalling.
DESCRIPTION:
If "chkconfig" rpm not present on the node then CPI installer not showing it in the prerequisite list of rpm while intsalling..
RESOLUTION:
Installer code modified.
INSTALLING THE PATCH
--------------------
1. Copy the hot-fix CPI_8.0.2_P20.pl to /tmp
2. Run installation scripts with the hot-fix
Example:
./installer -require /tmp/CPI_8.0.2_P20.pl
REMOVING THE PATCH
------------------
NONE
SPECIAL INSTRUCTIONS
--------------------
NONE
OTHERS
------
NONE
Applies to the following product releases
Update files
|
|
File name | Description | Version | Platform | Size |
|---|
Knowledge base
0
Troubleshooting and Resolving vxvm Service Startup Issues in RHEL 9
2025-04-07Problem In RHEL 9, the chkconfig package, which is used to manage legacy SysV init scripts, is not installed by default. This causes issues with services like Veritas Volume Manager (vxvm) that rely on SysV init scripts for startup. Additionally,...