charm changes nodename on upgrade causing rabbitmq cluster to break
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rabbitmq-server (Juju Charms Collection) |
Invalid
|
Critical
|
Unassigned |
Bug Description
We have observed that upgrading an existing 3 unit rabbitmq-server cluster to the latest stable charms can cause the cluster to break. This is because the charm will check that the rabbitmq-server (at least on the leader) is configured by ensuring that RABBITMQ_
;; ANSWER SECTION:
1.5.27.
1.5.27.
(see http://
The result is that a rabbitmq node whose nodename was originally configured with 172-27-5-1 now switches to ctrlnode1 which, when the charm attempts to restart rabbitmq, causes it to fail since it no longer recognises the nodename e.g. https:/
description: | updated |
Changed in rabbitmq-server (Juju Charms Collection): | |
assignee: | nobody → Jorge Niedbalski (niedbalski) |
Changed in rabbitmq-server (Juju Charms Collection): | |
assignee: | Jorge Niedbalski (niedbalski) → nobody |
For the record this was with MAAS 1.5.4.