Adding machine to Identity Suite Virtual Appliance fails with cluster clocks out of sync error

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

When attempting to add a new node to an existing Identity Suite Virtual Appliance (vApp) cluster via the dashboard, the deployment fails immediately. The setup page may refresh without adding the node, or the deployment logs will indicate that the clocks across cluster nodes are not synchronized.

Environment

Virtual Appliance 14.5

Cause

The Virtual Appliance deployment logic performs a mandatory validation check to ensure all nodes in the cluster have nearly identical system times. If there is a significant time drift between the existing nodes and the new node being added, the validation fails to prevent potential data inconsistency and handshake errors.

Resolution

1. Log in to the Virtual Appliance (vApp) console of the existing nodes and the new node.
2. Use the setTimeAndDate command to synchronize the date and time across all systems so they match exactly.
3. If the deployment continues to fail with the same error after synchronization, verify if the node was partially added to the deployment map. If so, remove the node (click the 'X' in the top right of the machine card in the Setup page) before retrying the deployment.
4. Retry the Add Machine and Deploy steps from the dashboard.
5. If the issue persists, collect the deployment logs from the node where the installation was initiated and open a support case.

Additional Information

You can use the alias "check_cluster_clock_sync" to check the time sync, see documentation Available Aliases

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.