cat /storage/db/casa/webapp/hsqldb/casa.db.script | grep -i online_stateINSERT INTO CASA_DOCS VALUES('clusterMembership','{"onlineState":"ONLINE","cluster_name":"cluster","is_ha_enabled":false,"ha_transition_state":null,"ca_state":"DISABLED","initialization_state":"NONE","remove_node_state":"NONE","document_version":22,"document_time":#######,"online_state":"ADDING"Aria Operations requires all nodes in a cluster to run the exact same version. If a new node is added with a different version (for example, adding an 8.18.6 node to an 8.18.2 cluster), internal communication and database synchronization will break. Because the versions do not match, the analytics service fails to start, leaving the new node stuck in an ADDING state and the existing cluster nodes stuck on Waiting for analytics.
To restore cluster health and complete the migration, follow these steps:
Decommission the Mismatched Node:
https://<FQDN>/admin).Stabilize the Cluster:
root user.casa serviceservice vmware-casa restart
Perform Corrective Expansion: