[Kolla][Kolla-Ansible] Unable to Deploy tacker victoria in centos 8 Stream

Richa Gupta gricha.1888 at gmail.com
Tue Apr 19 12:00:21 UTC 2022


We tried installing the tacker victoria release using Kolla Ansible
all-in-one deployment on centos stream 8, by using the following links:

https://docs.openstack.org/tacker/victoria/install/kolla.html

and running prerequisites mentioned in the link below:

https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html#install-dependencies

(We changed ussri to victoria at all necessary places. The globals.yml
exactly matches with the one given in the OpenStack link)

while running deployment we encounter the following error:

RUNNING HANDLER [Waiting for rabbitmq to start]
**********************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["docker", "exec",
"rabbitmq", "rabbitmqctl", "wait",
"/var/lib/rabbitmq/mnesia/rabbitmq.pid"], "delta": "0:00:10.704454", "end":
"2022-04-19 11:43:12.259809", "msg": "non-zero return code", "rc": 75,
"start": "2022-04-19 11:43:01.555355", "stderr": "Error: operation wait on
node rabbit at tacker-victoria timed out. Timeout value used: 10000",
"stderr_lines": ["Error: operation wait on node rabbit at tacker-victoria
timed out. Timeout value used: 10000"], "stdout": "Waiting for pid file
'/var/lib/rabbitmq/mnesia/rabbitmq.pid' to appear", "stdout_lines":
["Waiting for pid file '/var/lib/rabbitmq/mnesia/rabbitmq.pid' to appear"]}

RUNNING HANDLER [Restart remaining rabbitmq containers]
**************************************************************************************************

NO MORE HOSTS LEFT
***************************************************************************************************************************************

PLAY RECAP
***********************************************************************************************************************************************
localhost                  : ok=77   changed=43   unreachable=0    failed=1
   skipped=19   rescued=0    ignored=1

After this we run deploy again and encounter the following error:

TASK [service-rabbitmq : nova | Ensure RabbitMQ users exist]
***************************************************************************************************************************
FAILED - RETRYING: nova | Ensure RabbitMQ users exist (5 retries left).
FAILED - RETRYING: nova | Ensure RabbitMQ users exist (4 retries left).
FAILED - RETRYING: nova | Ensure RabbitMQ users exist (3 retries left).
FAILED - RETRYING: nova | Ensure RabbitMQ users exist (2 retries left).
FAILED - RETRYING: nova | Ensure RabbitMQ users exist (1 retries left).
failed: [localhost -> localhost] (item=None) => {"attempts": 5, "censored":
"the output has been hidden due to the fact that 'no_log: true' was
specified for this result", "changed": false}
fatal: [localhost -> {{ service_rabbitmq_delegate_host }}]: FAILED! =>
{"censored": "the output has been hidden due to the fact that 'no_log:
true' was specified for this result", "changed": false}

PLAY RECAP
*****************************************************************************************************************************************************************************
localhost                  : ok=116  changed=42   unreachable=0    failed=1
   skipped=40   rescued=0    ignored=0

Command failed ansible-playbook -i
/usr/local/share/kolla-ansible/ansible/inventory/all-in-one -e
@/etc/kolla/globals.yml  -e @/etc/kolla/passwords.yml -e
CONFIG_DIR=/etc/kolla  -e kolla_action=deploy
/usr/local/share/kolla-ansible/ansible/site.yml
[centos at tacker-victoria ~]$
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220419/8839a0e6/attachment.htm>


More information about the openstack-discuss mailing list