search

pegasystems / pega-helm-charts

Orchestrate a Pega Platform™ deployment by using Docker, Kubernetes, and Helm to take advantage of Pega Platform Cloud Choice flexibility.
https://community.pega.com/knowledgebase/articles/cloud-choice
Apache License 2.0
123 stars 197 forks source link

hazelcast Authentication failed or cluster name doesn't match #704

Closed SreecharanChallagundla closed 6 months ago

SreecharanChallagundla commented 7 months ago

Describe the bug When bringing up env after upgrading from v8.5.3 to v 8.8.3 we see the below issue -- Failed to authenticate the connection com.pega.hazelcast.v5.client.AuthenticationException: Authentication failed. The configured cluster name on the client (see ClientConfig.setClusterName()) does not match the one configured in the cluster or the credentials set in the Client security config could not be authenticated

To Reproduce deploy pega-web, pega-batch pods

Expected behavior As per the understanding, it needs to pick up the cluster name "prpchz" but it keeps on reporting name doesn't match.

SreecharanChallagundla commented 6 months ago

figured out issue.