Setting RabbitMQ NODENAME to non-FQDN breaks on MaaS 2.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack RabbitMQ Server Charm |
Fix Released
|
High
|
David Ames | ||
rabbitmq-server (Juju Charms Collection) |
Invalid
|
High
|
David Ames |
Bug Description
In `rabbit_utils.py` in `get_node_hostname` the nodename is requested to not be a FQDN:
nodename = get_hostname(
However, this causes issues with MaaS 2.0 because it has two PTR records for a single reverse DNS name.
This is an example entry:
```
53.69.189.
53.0-25.
53.0-25.
```
In our deployment it is picking up `eth0.unarrated
This leads to a `RABBITMQ_NODENAME` of `rabbit@eth0` which fails to resolve when it starts up.
Instead the entry should be set to `rabbit@
I tried using `RABBITMQ_
tags: | added: cpec |
tags: | added: canonical-bootstack |
tags: | added: sts |
tags: | added: conjure |
tags: | added: backport-potential |
Changed in rabbitmq-server (Juju Charms Collection): | |
status: | Fix Committed → Fix Released |
Changed in rabbitmq-server (Juju Charms Collection): | |
milestone: | 16.10 → 17.01 |
Changed in rabbitmq-server (Juju Charms Collection): | |
assignee: | James Page (james-page) → David Ames (thedac) |
status: | New → Fix Committed |
Changed in charm-rabbitmq-server: | |
assignee: | nobody → David Ames (thedac) |
importance: | Undecided → High |
status: | New → Fix Committed |
Changed in rabbitmq-server (Juju Charms Collection): | |
status: | Fix Committed → Invalid |
Changed in charm-rabbitmq-server: | |
milestone: | none → 17.02 |
Changed in charm-rabbitmq-server: | |
status: | Fix Committed → Fix Released |
For pretty formatting of the bug report: https:/ /gist.github. com/bertjwregee r/716d0c664142c 18f09b0f4dab1bd ad06