Error: Unable to login to analytics cluster VAN-Cluster with any of the ip(s)[10.70.75.3, 10.70.75.4]. This could be due to central-auth not configured properly
Steps to Verify:
1) Identify the default director for the tenant.
2) Analytics cluster reachable from the Concerto
If the analytics cluster is not reachable, then try to check below. If there are any failures, then check the network connectivity and if there is any firewall blocking the connectivity.
admin@versa-ecp:~$ nc -vz 10.70.75.3 8443
admin@versa-ecp:~$ nc -vz 10.70.75.4 8443
admin@versa-ecp:~$ ping 10.70.75.3
admin@versa-ecp:~$ ping 10.70.75.4
3) Check if Central-Auth is configured on the non-default directors. If not then create a Central-Auth with Default Authentication Connector.
In the Screenshot below: 10.73.40.1 and 10.73.40.2 are the Primary and Secondary IP addresses of the Default Director.
4) Verify, central auth is configured under Administrator > Organization > <Org-In-Q>
5) Once all the above is verified and configured, logout and login back to the concerto. Verify if the analytics cluster is accessible for the Non-Default director node.
Note:
Bug: 118175 and 148953
Description: Central-Auth: Central auth connection request going to the secondary director
Workaround: Remove the secondary director node IP from the Central-Auth connection. Verify the auth-token request from Non-Default director is going to the Default Primary Director and getting 200 response.
Logs to reference when tshooting on the director.
vnms-central-auth.log
access_log.log
vnms-spring-boot.log