Comment 2 for bug 2044248

Hello Markus and thanks for this bug report. If my understanding is correct, the logic currently implemented in the postinst script can cause problems when rabbitmq-server is used in a cluster configuration, with the cookie being a shared secret. If the cookie is replaced by a new random string, the cluster breaks. A "standalone" rabbitmq-server service won't be affected. Is this correct?

The postist logic comes from the Debian rabbitmq-server package. Ideally this bug should be discussed in Debian with the Debian maintainer of rabbitmq-server, who is the person who wrote [1]. Moreover, fixing the bug in Debian with benefit Debian and all its derivatives (including Ubuntu), without adding extra maintenance work (as an Ubuntu specific fix would do).

Would you be willing to file the bug against the Debian rabbitmq-server (source) package, and add a comment to this bug linking to the Debian bug? See "report bug" in [2].

Thanks!

[1] https://salsa.debian.org/openstack-team/third-party/rabbitmq-server/-/commit/c3c800b60bb7a878d58ea764d8b238e60184eac1
[2] https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=0;dist=unstable;ordering=normal;repeatmerged=0;src=rabbitmq-server