Ask Your Question
1

kolla-ansible deploy fail for rabbitmq

asked 2019-09-16 15:18:53 -0500

Xelaot gravatar image

Kolla-ansible deployment to all-in-one fails on "Waiting for rabbitmq to start on first node" due to "cannot exec in a stopped state: unknown"

I've gotten the same error with rocky and master

Full output here:

RUNNING HANDLER [rabbitmq : Waiting for rabbitmq to start on first node] ********************************************* fatal: [localhost]: FAILED! => {"changed": true, "cmd": "docker exec rabbitmq rabbitmqctl wait /var/lib/rabbitmq/mnesia/rabbitmq.pid", "delta": "0:00:00.380240", "end": "2019-09-16 10:40:17.794725", "msg": "non-zero return code", "rc": 126, "start": "2019-09-16 10:40:17.414485", "stderr": "", "stderr_lines": [], "stdout": "cannot exec in a stopped state: unknown", "stdout_lines": ["cannot exec in a stopped state: unknown"]}

Also the error of the container:

ERROR: epmd error for host openStack: address (cannot connect to host/port)

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2019-09-20 06:07:20 -0500

yoctozepto gravatar image

Please report a bug. AIO is regularly tested on all supported platforms and works out-of-the-box.

edit flag offensive delete link more
0

answered 2019-09-18 16:04:24 -0500

Xelaot gravatar image

Had to edit the RabbitMQ ansible config to hard code the api-interface

edit flag offensive delete link more

Comments

Could you clarify where you made a change? (And quite strange to run in to this STILL, when I'am using kolla-ansible from git (TRAIN release)...)

theque42 gravatar imagetheque42 ( 2019-12-10 14:54:42 -0500 )edit

in the kolla-ansible/ansible/roles/rabbitmq/templates/rabbitmq-env.conf.j2 file, replace the ERL_EMPD_ADDRESS with the ip address of your first network interface. I also put quotes around it and commented out the original line using a #.

Xelaot gravatar imageXelaot ( 2019-12-10 16:11:49 -0500 )edit

That way you are breaking the assumptions for multinode. You are both probably hit by https://bugs.launchpad.net/kolla-ansi... - please verify that is the case. RMQ is picky about IP address <> hostname matches.

yoctozepto gravatar imageyoctozepto ( 2019-12-11 01:43:24 -0500 )edit

If I understood that bug, it had to do with re-running kolla-ansible, and I hit this issue on first run/install. Additionally, my hosts file looks quite alright, although it has duplicate (correct) entries. Also worth mentioning, is I am running multinode setup, but with same error on both ctrls.

theque42 gravatar imagetheque42 ( 2019-12-11 07:05:09 -0500 )edit
theque42 gravatar imagetheque42 ( 2019-12-11 07:05:19 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-09-16 14:47:23 -0500

Seen: 441 times

Last updated: Sep 20 '19