contrail-docker - contrail-controller - contrail-ansible: rabbitmq does not support FQDN based setup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
High
|
Leela Bharath Kumar Kassetti | ||
R4.1 |
New
|
High
|
Leela Bharath Kumar Kassetti |
Bug Description
contrail-
- rabbitmq is down
- rabbitmq is trying to connect to a wrong interface (bond2, instead of br-bond2)
- hostname configuration is wrong in the rabbitmqctl status (fixed by editing /etc/rabbitmq/
- ansible manageded configuration in the docker image -> would update /etc/hosts, if the hostname would not be resolvable
- maas managed interfaces, hence they get resolved
- the ansible playbook has wrong assumption where it should cut the host entry from the DNS:
$ /contrail-
$ getent hosts 100.68.100.32 | awk '{print $2}' | cut -d . -f1
bond2
$ getent hosts 100.68.100.32 | awk '{print $2}'
bond2.4-
--> no such host as bond2 -> rabbitmq fails to startup
tags: | added: ansible |
information type: | Proprietary → Public |
Changed in juniperopenstack: | |
assignee: | nobody → Abhay Joshi (abhayj) |
Changed in juniperopenstack: | |
assignee: | Abhay Joshi (abhayj) → Leela Bharath Kumar Kassetti (klbharat) |
Changed in juniperopenstack: | |
importance: | Critical → High |
could be done similar to the other rabbitmq charms: add the hostname with the binding IP address to the /etc/hosts file to be sure that it goes over the selected interface (and not to depend on the FQDN configuration)