Post Kubernetes cluster restart, flexsnap-listener pod went into CrashLoopBackoff state or pods were unable to connect to flexsnap-rabbitmq

After Kubernetes cluster restart, flexsnap-listener pod went into CrashLoopBackoff state or pods such as flexsnap-coordinator, flexsnap-agent and so on were unable to connect to flexsnap-rabbitmq.

This issue can be resolved by restarting the NetBackup Snapshot Manager services in the following order using the kubectl delete <pod-name> -n <namespace> command:

flexsnap-certauth

flexsnap-rabbitmq

flexsnap-postgres

flexsnap-listener and so on.