Ask Your Question
2

kolla-ansible deploy need to be restarted many times

asked 2018-02-23 08:25:33 -0500

sinan gravatar image

updated 2018-02-23 08:26:47 -0500

Command kolla-ansible -i ./multinode deploy fails many times because of container configuration step exit the program. For instance, for mariadb container, it fails first time :

TASK [mariadb : Running MariaDB bootstrap container] fatal: [kolla4]: FAILED! => {"changed": true, "msg": "Container exited with non-zero return code"}

Docker logs of mariadb shows that mariadb configuration has been run and has exited sucessfully. Container should not exit after configuration !

If I launch this command a second times, it starts mariadb and it carries on deploying... Until the next container, RabbitMQ fails for the same reason. After relaunching, mariadb passes, rabbitmq passes, and keystone fails. And so on (glance, cinder, nova, etc.).

Deployment works but I need to relaunch it many times.

Kolla-ansible Version: 5.0.1 / Openstack docker tag: pike

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
2

answered 2018-02-26 05:26:59 -0500

Hi, problem is with docker-py version

For pike and before use docker==2.6, master have the fix for that issue.

For previous version fix is waiting to be released with next kolla tag.

Regards

edit flag offensive delete link more

Comments

And here is the fix https://review.openstack.org/#/c/539988/, which will be released recently.

Jeffrey4l gravatar imageJeffrey4l ( 2018-02-26 09:46:24 -0500 )edit

the fix may be in that link, but how can I confirm I have the proper version? Also, how would we use docker==2.6 in the kolla-ansible buildout? Says it's been merged now, but still not working for me. Should we be changing something in ansible or the kolla files? would we need to pull source?

khrystoph gravatar imagekhrystoph ( 2018-03-06 21:20:11 -0500 )edit

In stable branch the fix is not released until the next tag is created. Should be already if using stable/pike from git instead of pip

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2018-03-07 01:08:06 -0500 )edit
0

answered 2018-10-03 13:39:02 -0500

Kookus gravatar image

Hi,

I have the same problem, we had a controller and We decided to put three. So I've done all process through kolla-ansible deploy. We Added in our inventory two machines more before running kolla-ansible -i inventary deploy.

So In two controllers, one new and another already existed in my openstack, the rabbitmq starts and works perfectly, but in the last one... unfortunately, it doesn't work.

Rabbitmq container is restarted over and over.... and it doesn't show any error. The only messages in docker log is:

+ sudo -E kolla_set_configs INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json INFO:__main__:Validating config file INFO:__main__:Kolla config strategy set to: COPY_ALWAYS INFO:__main__:Copying service configuration files INFO:__main__:Deleting /etc/rabbitmq/rabbitmq-env.conf INFO:__main__:Copying /var/lib/kolla/config_files/rabbitmq-env.conf to /etc/rabbitmq/rabbitmq-env.conf INFO:__main__:Setting permission for /etc/rabbitmq/rabbitmq-env.conf INFO:__main__:Deleting /etc/rabbitmq/rabbitmq.config INFO:__main__:Copying /var/lib/kolla/config_files/rabbitmq.config to /etc/rabbitmq/rabbitmq.config INFO:__main__:Setting permission for /etc/rabbitmq/rabbitmq.config INFO:__main__:Deleting /etc/rabbitmq/rabbitmq-clusterer.config INFO:__main__:Copying /var/lib/kolla/config_files/rabbitmq-clusterer.config to /etc/rabbitmq/rabbitmq-clusterer.config INFO:__main__:Setting permission for /etc/rabbitmq/rabbitmq-clusterer.config INFO:__main__:Deleting /etc/rabbitmq/definitions.json INFO:__main__:Copying /var/lib/kolla/config_files/definitions.json to /etc/rabbitmq/definitions.json INFO:__main__:Setting permission for /etc/rabbitmq/definitions.json INFO:__main__:Writing out command to execute INFO:__main__:Setting permission for /var/lib/rabbitmq INFO:__main__:Setting permission for /var/lib/rabbitmq/mnesia INFO:__main__:Setting permission for /var/lib/rabbitmq/.erlang.cookie INFO:__main__:Setting permission for /var/lib/rabbitmq/mnesia/rabbit@br-in... INFO:__main__:Setting permission for /var/lib/rabbitmq/mnesia/rabbit@br-in... INFO:__main__:Setting permission for /var/log/kolla/rabbitmq ++ cat /run_command + CMD=/usr/sbin/rabbitmq-server + ARGS= + [[ ! -n '' ]] + . kolla_extend_start ++ : /var/log/kolla/rabbitmq ++ [[ -n '' ]] ++ [[ ! -d /var/log/kolla/rabbitmq ]] +++ stat -c %a /var/log/kolla/rabbitmq ++ [[ 755 != \7\5\5 ]] + echo 'Running command: '\''/usr/sbin/rabbitmq-server'\''' Running command: '/usr/sbin/rabbitmq-server' + exec /usr/sbin/rabbitmq-server =INFO REPORT==== 3-Oct-2018::15:00:13 === Clusterer stopping node now.

Someone Can help me deal with problem?

Thank you!

edit flag offensive delete link more

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

2 followers

Stats

Asked: 2018-02-23 08:25:33 -0500

Seen: 717 times

Last updated: Feb 26 '18