IDM 15 IGX Cluster Secondary Node Services Not Installed – Node Versions Out of Sync
search cancel

IDM 15 IGX Cluster Secondary Node Services Not Installed – Node Versions Out of Sync

book

Article ID: 436603

calendar_today

Updated On:

Products

CA Identity Manager

Issue/Introduction

While configuring a new IGA Express (IGX) cluster environment with Identity Manager 15, the following issues occur after adding a secondary node to the cluster:

The Identity Manager, Balancer, and UserStore Proxy components fail to install on the secondary node after being added via the IGX Dashboard.
The IGX Dashboard displays the error message: "Node versions are out of sync!"
The secondary node may not be visible or fully synchronized within the dashboard topology.

Environment

IGA Xpress 1.0
IGA Suite v15

Cause

The primary cause is an environment-level failure during the initial node synchronization process. Specifically, low disk space on the secondary node causes the synchronization of the localchan (local channel) to fail. Because the local synchronization is incomplete, the node cannot report the correct versioning information to the cluster leader, resulting in the "out of sync" error and blocking service installation.

Resolution

To resolve this issue and successfully install services on the secondary node, follow these steps:

Increase Disk Space: Ensure the secondary node has sufficient disk space to accommodate the IGA Express installation and the synchronization of local configuration channels.
Reinstall IGA Express: If the previous installation was corrupted due to disk space issues, perform a clean installation of the IGA Express (igaxpress) package on the secondary node.
Re-join the Cluster: Add the secondary node back to the cluster via the IGX Dashboard.
Verify Node Visibility: Confirm that the secondary node is fully visible and listed with a healthy status in the IGX Dashboard before attempting to deploy services.
Deploy Components: Once the node is synchronized and visible, drag and drop the Identity Manager, Balancer, and UserStore Proxy components to the secondary node.
Configuration: Proceed with the service configuration as required.