Cannot add more than one unit on openstack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack RabbitMQ Server Charm |
Expired
|
Medium
|
Unassigned | ||
rabbitmq-server (Juju Charms Collection) |
Invalid
|
Medium
|
Unassigned |
Bug Description
This is possibly specific to the Canonical PS4 openstack environment (or specifically, the dns resolution there), but it may be better if rabbitmq defaulted to IP addresses for RABBITMQ_NODENAME.
Steps to reproduce:
1) Deploy rabbitmq-server into a fresh openstack environment
2) Add a second unit
3) Wait and check the status.
Expected result: new node has joined the cluster.
Actual result: cluster-
I initially saw it with r82 of the charm - so reproduced it again just now there [1] (example plus full details of error), but also checked and verified the same issue with r99 [2]
pjdc says that the bad hostname is likely from the reverse dns,
[1] http://
[2] http://
description: | updated |
Changed in rabbitmq-server (Juju Charms Collection): | |
status: | Incomplete → Confirmed |
Changed in charm-rabbitmq-server: | |
importance: | Undecided → Medium |
status: | New → Incomplete |
Changed in rabbitmq-server (Juju Charms Collection): | |
status: | Incomplete → Invalid |
Michael, i've had a quick go at deploying lp:charms/trusty/rabbitmq-server using the local_provider and the steps you specify and I am not seeing this problem. I have also regularly deployed to openstack in the last few days and am not seeing an issue there either. Could i ask you to provide your rabbitmq juju logs e.g. /var/log/ juju/unit- rabbitmq- server- 0.log from all your units and also give me the service name of your deployed rabbitmq service and the hostnames of the nodes deployed to. Thanks.