Rabbitmq is not using the configured NODENAME

Description

The NODENAME we set in rabbitmq-env.conf isn't used because we moved the conf file, but didn't provide the new location to rabbitmq in env vars.
This means rabbitmq is going to use the automatically-inferred nodename, which changes after a hostname change, so items like rabbitmq users and policies won't be used after a hostname change.
This breaks docker images (and regular images, if a new vm changes the hostname), because containers usually run with a new hostname

Assignee

Łukasz Maksymczuk

Reporter

Łukasz Maksymczuk

Labels

None

Bug Type

None

Target Version

None

Severity

None

Fix versions

Affects versions

Configure