Hi @koushik.halder! I have some ideas on what is going on here, but to narrow the focus a little can I have you share what version of Conjur you are working with, what actions were carried out in the environment prior to encountering this issue, and the contents of /etc/chef/solo.json on each of the nodes in your cluster? (scrub the server names from these files if any are present)
Please @ me when you reply so that I get notified.
I ran into an issue “Conjur Standby Nodes rebuild issue”
Here the /etc/chef/solo.json has an additional host into cluster member list, however we have not enrolled it by evoking the command but updating the cluster policy.
As a result, unable to rebuild the node to add into the cluster, could you please check.
We are having a cluster of 3 nodes, the master got failover to a new node, while trying to rebuild the standby, after creating the seed file for the new standby by, the /etc/chef/solo.json got the application name of the master instead of its own node, is something wrong here ?