|
---|
Release type: | Patch |
Release date: | 2019-12-30 |
OS update support: | RHEL8 x86-64 Update 1 |
Technote: | None |
Documentation: | None |
Popularity: | 4077 viewed downloaded |
Download size: | 149.33 MB |
Checksum: | 2171181381 |
InfoScale Availability 7.4.1 On RHEL8 x86-64
InfoScale Enterprise 7.4.1 On RHEL8 x86-64 InfoScale Foundation 7.4.1 On RHEL8 x86-64 InfoScale Storage 7.4.1 On RHEL8 x86-64 |
None.
|
3984139, 3984731, 3988238, 3988843, 3989413, 3989416, 3990017, 3990018, 3990019, 3990020, 3990021, 3990049
|
VRTSodm-7.4.1.1600-RHEL8
VRTSvxfs-7.4.1.1600-RHEL8 VRTSllt-7.4.1.1600-RHEL8 VRTSgab-7.4.1.1600-RHEL8 VRTSvxfen-7.4.1.1600-RHEL8 VRTSamf-7.4.1.1600-RHEL8 VRTSdbac-7.4.1.1600-RHEL8 VRTSaslapm-7.4.1.1600-RHEL8 VRTSvxvm-7.4.1.1600-RHEL8 |
* * * READ ME * * * * * * InfoScale 7.4.1 * * * * * * Patch 1600 * * * Patch Date: 2019-12-26 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 * KNOWN ISSUES PATCH NAME ---------- InfoScale 7.4.1 Patch 1600 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- RHEL8 x86-64 PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSamf VRTSaslapm VRTSdbac VRTSgab VRTSllt VRTSodm VRTSvxfen VRTSvxfs VRTSvxvm 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: VRTSvxfs-7.4.1.1600 * 3989413 (3989412) VxFS module failed to load on RHEL8.1 Patch ID: VRTSvxvm-7.4.1.1600 * 3984139 (3965962) No option to disable auto-recovery when a slave node joins the CVM cluster. * 3988238 (3988578) Encrypted volume creation fails on RHEL 8 * 3984731 (3984730) VxVM logs warning messages when the VxDMP module is stopped or removed for the first time after the system is rebooted * 3988843 (3989796) RHEL 8.1 support for VxVM Patch ID: VRTSaslapm-7.4.1.1600 * 3990049 (3990048) ASLAPM rpm Support on RHEL 8.1 kernel Patch ID: VRTSdbac-7.4.1.1600 * 3990021 (3990016) Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). Patch ID: VRTSamf-7.4.1.1600 * 3990020 (3990016) Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). Patch ID: VRTSvxfen-7.4.1.1600 * 3990019 (3990016) Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). Patch ID: VRTSgab-7.4.1.1600 * 3990018 (3990016) Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). Patch ID: VRTSllt-7.4.1.1600 * 3990017 (3990016) Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). Patch ID: VRTSodm-7.4.1.1600 * 3989416 (3989415) ODM module failed to load on RHEL8.1 DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following incidents: Patch ID: VRTSvxfs-7.4.1.1600 * 3989413 (Tracking ID: 3989412) SYMPTOM: VxFS module failed to load on RHEL8.1 DESCRIPTION: The RHEL8.1 is new release and it has some changes in kernel which caused VxFS module failed to load on it. RESOLUTION: Added code to support VxFS on RHEL8.1. Patch ID: VRTSvxvm-7.4.1.1600 * 3984139 (Tracking ID: 3965962) SYMPTOM: No option to disable auto-recovery when a slave node joins the CVM cluster. DESCRIPTION: In a CVM environment, when the slave node joins the CVM cluster, it is possible that the plexes may not be in sync. In such a scenario auto-recovery is triggered for the plexes. If a node is stopped using the hastop -all command when the auto-recovery is in progress, the vxrecover operation may hang. An option to disable auto-recovery is not available. RESOLUTION: The VxVM module is updated to allow administrators to disable auto-recovery when a slave node joins a CVM cluster. A new tunable, auto_recover, is introduced. By default, the tunable is set to 'on' to trigger the auto-recovery. Set its value to 'off' to disable auto-recovery. Use the vxtune command to set the tunable. * 3988238 (Tracking ID: 3988578) SYMPTOM: Encrypted volume creation fails on RHEL 8 DESCRIPTION: On the RHEL 8 platform, python3 gets installed by default. However, the Python script that is used to create encrypted volumes and to communicate with the Key Management Service (KMS) is not compatible with python3. Additionally, an 'unsupported protocol' error is reported for the SSL protocol SSLv23 that is used in the PyKMIP library to communicate with the KMS. RESOLUTION: The python script is made compatible with python2 and python3. A new option ssl_version is made available in the /etc/vx/enc-kms-kmip.conf file to represent the SSL version to be used by the KMIP client. The 'unsupported protocol' error is addressed by using the protocol version PROTOCOL_TLSv1. The following is an example of the sample configuration file: [client] host = kms-enterprise.example.com port = 5696 keyfile = /etc/vx/client-key.pem certfile = /etc/vx/client-crt.pem cacerts = /etc/vx/cacert.pem ssl_version = PROTOCOL_TLSv1 * 3984731 (Tracking ID: 3984730) SYMPTOM: VxVM logs warning messages when the VxDMP module is stopped or removed for the first time after the system is rebooted. DESCRIPTION: VxVM logs these warnings because the QUEUE_FLAG_REGISTERED and QUEUE_FLAG_INIT_DONE queue flags are not cleared while registering the dmpnode. The following stack is reported after stopping/removing VxDMP for first time after every reboot: kernel: WARNING: CPU: 28 PID: 33910 at block/blk-core.c:619 blk_cleanup_queue+0x1a3/0x1b0 kernel: CPU: 28 PID: 33910 Comm: modprobe Kdump: loaded Tainted: P OE ------------ 3.10.0-957.21.3.el7.x86_64 #1 kernel: Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 10/02/2018 kernel: Call Trace: kernel: [<ffffffff9dd63107>] dump_stack+0x19/0x1b kernel: [<ffffffff9d697768>] __warn+0xd8/0x100 kernel: [<ffffffff9d6978ad>] warn_slowpath_null+0x1d/0x20 kernel: [<ffffffff9d944b03>] blk_cleanup_queue+0x1a3/0x1b0 kernel: [<ffffffffc0cd1f3f>] dmp_unregister_disk+0x9f/0xd0 [vxdmp] kernel: [<ffffffffc0cd7a08>] dmp_remove_mp_node+0x188/0x1e0 [vxdmp] kernel: [<ffffffffc0cd7b45>] dmp_destroy_global_db+0xe5/0x2c0 [vxdmp] kernel: [<ffffffffc0cde6cd>] dmp_unload+0x1d/0x30 [vxdmp] kernel: [<ffffffffc0d0743a>] cleanup_module+0x5a/0xd0 [vxdmp] kernel: [<ffffffff9d71692e>] SyS_delete_module+0x19e/0x310 kernel: [<ffffffff9dd75ddb>] system_call_fastpath+0x22/0x27 kernel: --[ end trace fd834bc7817252be ]-- RESOLUTION: The queue flags are modified to handle this situation and not to log such warning messages. * 3988843 (Tracking ID: 3989796) SYMPTOM: Existing package failed to load on RHEL 8.1 setup. DESCRIPTION: RHEL 8.1 is a new release and hence VxVM module is compiled with this new kernel along with few other changes . RESOLUTION: changes have been done to make VxVM compatible with RHEL 8.1 Patch ID: VRTSaslapm-7.4.1.1600 * 3990049 (Tracking ID: 3990048) SYMPTOM: Support for ASLAPM on RHEL 8.1 kernel DESCRIPTION: The RHEL8.1 is new release and hence APM module should be recompiled with new kernel. RESOLUTION: Compiled APM with new kernel. Patch ID: VRTSdbac-7.4.1.1600 * 3990021 (Tracking ID: 3990016) SYMPTOM: Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). DESCRIPTION: Veritas Cluster Server does not support Red Hat Enterprise Linux versions later than RHEL8.0 . RESOLUTION: Veritas Cluster Server support for Red Hat Enterprise Linux 8 Update 1(RHEL8.1) is now introduced. Patch ID: VRTSamf-7.4.1.1600 * 3990020 (Tracking ID: 3990016) SYMPTOM: Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). DESCRIPTION: Veritas Cluster Server does not support Red Hat Enterprise Linux versions later than RHEL8.0 . RESOLUTION: Veritas Cluster Server support for Red Hat Enterprise Linux 8 Update 1(RHEL8.1) is now introduced. Patch ID: VRTSvxfen-7.4.1.1600 * 3990019 (Tracking ID: 3990016) SYMPTOM: Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). DESCRIPTION: Veritas Cluster Server does not support Red Hat Enterprise Linux versions later than RHEL8.0 . RESOLUTION: Veritas Cluster Server support for Red Hat Enterprise Linux 8 Update 1(RHEL8.1) is now introduced. Patch ID: VRTSgab-7.4.1.1600 * 3990018 (Tracking ID: 3990016) SYMPTOM: Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). DESCRIPTION: Veritas Cluster Server does not support Red Hat Enterprise Linux versions later than RHEL8.0 . RESOLUTION: Veritas Cluster Server support for Red Hat Enterprise Linux 8 Update 1(RHEL8.1) is now introduced. Patch ID: VRTSllt-7.4.1.1600 * 3990017 (Tracking ID: 3990016) SYMPTOM: Veritas Cluster Server does not support Red Hat Enterprise Linux 8 Update 1(RHEL8.1). DESCRIPTION: Veritas Cluster Server does not support Red Hat Enterprise Linux versions later than RHEL8.0 . RESOLUTION: Veritas Cluster Server support for Red Hat Enterprise Linux 8 Update 1(RHEL8.1) is now introduced. Patch ID: VRTSodm-7.4.1.1600 * 3989416 (Tracking ID: 3989415) SYMPTOM: ODM module failed to load on RHEL8.1 DESCRIPTION: The RHEL8.1 is new release and it has some changes in kernel which caused ODM module failed to load on it. RESOLUTION: Added code to support ODM on RHEL8.1 INSTALLING THE PATCH -------------------- Run the Installer script to automatically install the patch: ----------------------------------------------------------- Please be noted that the installation of this P-Patch will cause downtime. To install the patch perform the following steps on at least one node in the cluster: 1. Copy the patch infoscale-rhel8_x86_64-Patch-7.4.1.1600.tar.gz to /tmp 2. Untar infoscale-rhel8_x86_64-Patch-7.4.1.1600.tar.gz to /tmp/hf # mkdir /tmp/hf # cd /tmp/hf # gunzip /tmp/infoscale-rhel8_x86_64-Patch-7.4.1.1600.tar.gz # tar xf /tmp/infoscale-rhel8_x86_64-Patch-7.4.1.1600.tar 3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.) # pwd /tmp/hf # ./installVRTSinfoscale741P1600 [<host1> <host2>...] You can also install this patch together with 7.4.1 base release using Install Bundles 1. Download this patch and extract it to a directory 2. Change to the Veritas InfoScale 7.4.1 directory and invoke the installer script with -patch_path option where -patch_path should point to the patch directory # ./installer -patch_path [<path to this patch>] [<host1> <host2>...] Install the patch manually: -------------------------- Manual installation is not recommended. REMOVING THE PATCH ------------------ Manual uninstallation is not recommended. KNOWN ISSUES ------------ * Tracking ID: 3990473 SYMPTOM: Systems may panic when resize operation is performed on a disk initialized as a simple disk WORKAROUND: No workaround available to resolve this issue. * Tracking ID: 3990925 SYMPTOM: Can not use native DMP support for data VG and for root VG. WORKAROUND: out of 3 issues, 2 issues fixed and working on 3rd issue. * Tracking ID: 3991769 SYMPTOM: RHEL8.1 - Seen Kernel Warning WARN_ONCE - "no blkg associated for bio on block-device" in dmesg during the direct I/O to the underlying device sometimes. WORKAROUND: No workaround available to resolve this kernel warning. * Tracking ID: 3991770 SYMPTOM: [BUG] IO hang observed on RHEL8.0 /8.1 when underlying devices are set to lower queue depth compared to blk_mq registered queue depth for the device. IO throttling is not happening properly at OS layer, this leads to IO hang in case of IO stress. WORKAROUND: No workaround available to resolve this OS issue. * Tracking ID: 3986388 SYMPTOM: Online migration from native file system to VxFS is not supported for RHEL 8 and RHEL8.1. WORKAROUND: None * Tracking ID: 3989317 SYMPTOM: The Filesystem log replay may get stuck if fsck command results in crash or core dump during cluster reconfiguration. WORKAROUND: Manually terminate the process that runs the fsck command to proceed with the cluster reconfiguration and to make file system accessible again. SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE |
Why Register?
Get notifications about ASLs/APMs, HCLs, patches, and high availability agents
As a registered user, you can create notifications to receive updates about NetBackup Future Platform and Feature Plans, NetBackup hot fixes/EEBs in released versions, Array Support Libraries (ASLs)/Array Policy Modules (APMs), hardware compatibility lists (HCLs), patches and high availability agents. In addition, you can create system-specific notifications customized to your environment.
Compare configurations
The Compare Configurations feature lets you compare different system scans by the data collector. When you sign in, you can choose a target system, compare reports run at different times, and easily see how the system's configuration has changed.
Save configurations
After logging in, you can retrieve past reports, share reports with colleagues, review notifications you received, and retain custom settings. Anonymous users cannot access these features.
Bulk uploader
As a registered user,you can upload multiple reports, using the Bulk Uploader.