7.4

Cause
Starting in version 7.3, the vRealize Automation appliance can support dual NICs. However, the
engineering template on which the appliance is based prevents the management interface from working
properly until you apply the solution.
Solution
After adding an additional NIC, restart the vRealize Automation appliance.
Cannot Promote a Secondary Virtual Appliance to Master
In vRealize Automation, low virtual appliance memory might prevent virtual appliance promotions in the
cluster.
Problem
The master node runs low on memory. You log in to its management interface Database page, and try to
promote a secondary node to become the new master. The following error occurs.
Fail to execute on Node node-name, host is master-FQDN
because of: Could not read remote lock command result for node: node-name
on address: master-FQDN, reason is: 500 Internal Server Error
Cause
Promotion only succeeds when all nodes can confirm reconfiguration to a newly promoted master. The
low memory prevents the old master from confirming, even though all nodes are reachable.
Solution
Power off the master node that has low memory. Log in to the secondary node management interface
Database page, and promote the secondary node.
Active Directory Sync Log Retention Time Is Too Short
In vRealize Automation, the Active Directory Sync logs go back only a couple days.
Problem
After two days, Active Directory Sync logs disappear from the management interface. Folders for the logs
also disappear from the following vRealize Automation appliance directory.
/db/elasticsearch/horizon/nodes/0/indices
Cause
To conserve space, vRealize Automation sets the maximum retention time for Active Directory Sync logs
to three days.
Solution
1 Log in to a console session on the vRealize Automation appliance as root.
Installing vRealize Automation
VMware, Inc. 166