Issues related to the VCS engine
This section describes the knonw issues about the VCS engine.
Related information
Cluster Server known issues
Extremely high CPU utilization may cause HAD to fail to heartbeat to GABMissing host names in engine_A.log file (1919953)The hacf -cmdtocf command generates a broken main.cf fileCharacter corruption observed when executing the uuidconfig.pl -clus -display -use_llthost commandTrigger does not get executed when there is more than one leading or trailing slash in the triggerpathService group is not auto started on the node having incorrect value of EngineRestartedGroup is not brought online if top level resource is disabledNFS resource goes offline unexpectedly and reports errors when restartedParent group does not come online on a node where child group is onlineCannot modify temp attribute when VCS is in LEAVING stateOracle service group faults on secondary site during failover in a disaster recovery scenarioService group may fail to come online after a flush and a force flush operationElevated TargetCount prevents the online of a service group with hagrp -online -sys commandAuto failover does not happen in case of two successive primary and secondary cluster failuresGCO clusters remain in INIT stateThe ha commands may fail for non-root user if cluster is secureStartup trust failure messages in system logsRunning -delete -keys for any scalar attribute causes core dumpVeritas InfoScale enters into admin_wait state when Cluster Statistics is enabled with load and capacity definedAgent reports incorrect state if VCS is not set to start automatically and utmp file is empty before VCS is startedVCS crashes if feature tracking file is corruptRemoteGroup agent and non-root users may fail to authenticate after a secure upgradeIf you disable security before upgrading VCS to version 7.0.1 or later on secured clusters, the security certificates will not be upgraded to 2048 bit SHA2Java console and CLI do not allow adding VCS user names starting with '_' character (3870470)