Yes, I think this is a rabbitmq-server packaging bug if the package itself is replacing the .erlang.cookie file in a clustered installation. It will indeed break the cluster as the readme calls out.
Yes, I think this is a rabbitmq-server packaging bug if the package itself is replacing the .erlang.cookie file in a clustered installation. It will indeed break the cluster as the readme calls out.