Description

Veritas engineering has created a new method to update the /etc/VRTSvcs/conf/config/types.cf file for Veritas Cluster Server (VCS) environments. Traditionally, users had to copy the types.cf file from /etc/VRTSvcs/conf/ to /etc/VRTSvcs/conf/config.
 

When installing the VRTSvcsag (Agent Pack) rpm, the following message was reported:
 

# rpm -Uvh VRTSvcsag-7.4.2.3300-RHEL8.x86_64.rpm
Verifying... ################################# [100%]
Preparing... ################################# [100%]
Updating / installing...
1:VRTSvcsag-7.4.2.3300-RHEL8 ################################# [100%]
Leaving existing types.cf for configuration
Implement /etc/VRTSvcs/conf/types.cf to utilize resource type updates

To ensure the /etc/VRTSvcs/conf/config/types.cf file is updated correctly and does not remove any customized resource entries.


A new trigger script has been created with the following 2 x Private hotfixes:

vcsag-rhel8_x86_64-HotFix-7.4.2.3501
vcs-rhel8_x86_64-HotFix-7.4.2.3501 

SYMPTOM:
When upgrading the VRTSvcsag rpm/package, the Veritas Cluster Server (VCS) /etc/VRTSvcs.conf/config/types.cf file can be updated incorrectly.

DESCRIPTION:
When upgrading the VRTSvcsag rpm/package, the Veritas Cluster Server (VCS) /etc/VRTSvcs.conf/config/types.cf file can be updated incorrectly. During some instances, the user may be informed to manually copy the /etc/VRTSvcs/conf/types.cf over the /etc/VRTSvcs/conf/config/types.cf file. Need to remove simply the message "Implement /etc/VRTSvcs/conf/types.cf to utilize resource type updates" when updating the VRTSvcsag rpm

RESOLUTION:
To ensure the /etc/VRTSvcs/conf/config/types.cf file is updated correctly following VRTSvcsag updates, the script user_trigger_update_types can be manually triggered by the user and will change existing message with new one mention below:
Leaving existing /etc/VRTSvcs/conf/config/types.cf configuration file unmodified
Copy /opt/VRTSvcs/bin/sample_triggers/VRTSvcs/user_trigger_update_types to /opt/VRTSvcs/bin/triggers
To manually update the types.cf, execute command "hatrigger -user_trigger_update_types 0
 

The supported hotfixes have been made available for this issue. Please contact Veritas Technical Support to obtain this fix. This hotfix has not yet gone through any extensive Q&A testing. Consequently, if you are not adversely affected by this problem and have a satisfactory temporary workaround in place, we recommend that you wait for the public release of this hotfix.

Veritas Technologies LLC currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Veritas’ plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.

New message format:
 

Leaving existing /etc/VRTSvcs/conf/config/types.cf configuration file unmodified
Copy /opt/VRTSvcs/bin/sample_triggers/VRTSvcs/user_trigger_update_types to /opt/VRTSvcs/bin/triggers
To manually update the types.cf, execute command "hatrigger -user_trigger_update_types 0

Steps:
 

The new trigger user_trigger_update_types script will be available in /opt/VRTSvcs/bin/sample_triggers/VRTSvcs with the updated VRTSvcsag rpm and needs to be manually copied to /opt/VRTSvcs/bin/triggers.

# cp /opt/VRTSvcs/bin/sample_triggers/VRTSvcs/user_trigger_update_types  /opt/VRTSvcs/bin/triggers/

Once copied, the user will need to execute below syntax:

# /opt/VRTSvcs/bin/hatrigger -user_trigger_update_types triggertype

Note: Triggertype "0" is to cater for a custom trigger.

Syntax:

# /opt/VRTSvcs/bin/hatrigger -user_trigger_update_types 0
VCS WARNING V-16-1-10416 Attribute already exists 'EnableSSL' (Apache)
VCS WARNING V-16-1-10416 Attribute already exists 'DelayAfterOnline' (Application)
VCS WARNING V-16-1-10416 Attribute already exists 'DelayAfterOffline' (Application)
VCS WARNING V-16-1-10416 Attribute already exists 'RefreshInterval' (DNS)
VCS WARNING V-16-1-10416 Attribute already exists 'PanicSystemOnDGLoss' (DiskGroup)
VCS WARNING V-16-1-10416 Attribute already exists 'UmountVolumes' (DiskGroup)
VCS WARNING V-16-1-10416 Attribute already exists 'ClearClone' (DiskGroup)
VCS WARNING V-16-1-10416 Attribute already exists 'OptCheck' (Mount)
VCS WARNING V-16-1-10416 Attribute already exists 'CreateMntPt' (Mount)
VCS WARNING V-16-1-10416 Attribute already exists 'ReuseMntPt' (Mount)
VCS WARNING V-16-1-10416 Attribute already exists 'AccessPermissionChk' (Mount)
VCS WARNING V-16-1-10416 Attribute already exists 'Lower' (NFSRestart)
VCS WARNING V-16-1-10416 Attribute already exists 'AutoResync' (RVGPrimary)
VCS WARNING V-16-1-10416 Attribute already exists 'ResyncType' (RVGPrimary)
VCS WARNING V-16-1-10416 Attribute already exists 'BunkerSyncElapsedTime' (RVGPrimary)
VCS WARNING V-16-1-10416 Attribute already exists 'AutoResync' (RVGSharedPri)
VCS WARNING V-16-1-10416 Attribute already exists 'ResyncType' (RVGSharedPri)
VCS WARNING V-16-1-10416 Attribute already exists 'OptCheck' (SambaServer)
VCS WARNING V-16-1-10416 Attribute already exists 'MonitorOption' (ASMInst)
VCS WARNING V-16-1-10416 Attribute already exists 'MonitorOption' (Oracle)

 

The /etc/VRTSvcs/conf/config/types.cf will now contain the updated resource definitions.