Hazelcast cluster is not formed after upgrading VIP Auth Hub

Products

• VIP Authentication Hub

Issue/Introduction

When upgrading to  AuthHub 2.2.2  and after deployment of hazelcast cluster, the Hazelcast cluster is not formed where only one IP in the cluster is observed whereas 3 replicas for the Hazelcast should be available ( 3 IPs) 

Members {size:1, ver:1} [
   Member [10.x.x.x]:5702 - 3a84adcc-b7ab-*********** this
]

Environment

AuthHub 2.2

Resolution

Hazelcast uses port 5702 and issue was caused since the port 5702 was not allowed in the policy.

After allowing port 5702, the cluster was formed properly and 3 IPs were observed from the logs for all three Hazelcast pods.