Ask Your Question

sinan's profile - activity

2018-03-06 21:23:24 -0500 received badge  Nice Question (source)
2018-03-06 21:17:25 -0500 received badge  Famous Question (source)
2018-02-26 08:43:32 -0500 received badge  Student (source)
2018-02-26 06:58:45 -0500 received badge  Notable Question (source)
2018-02-26 05:27:08 -0500 received badge  Popular Question (source)
2018-02-23 08:25:33 -0500 asked a question kolla-ansible deploy need to be restarted many times

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

2018-02-23 07:53:54 -0500 received badge  Famous Question (source)
2016-05-02 00:54:16 -0500 received badge  Notable Question (source)
2015-11-29 03:43:50 -0500 received badge  Popular Question (source)
2015-10-14 05:11:24 -0500 received badge  Editor (source)
2015-10-13 08:49:14 -0500 asked a question Deploy hdp with Openstack Sahara: Failed to set the hostname

I'm trying to deploy an hadoop cluster with HDP (2.0.6) thanks to sahara (openstack Kilo release).

After VM are started up, instance log shows:

cloud-init[640]: 2015-10-12 18:37:11,264 -[WARNING]: Failed to set the hostname to hdp-test-namenode-001.novalocal (hdp-test-namenode-001)

and sahara logs show:

Can't login to node hdp-test-namenode-001, reason AuthenticationException: Authentication failed. _is_accessible /usr/lib/python2.7/site-packages/sahara/service/ If I set hostname manually in the vm provisionned by sahara, sahara can connect by ssh and continues to next step. So, there is a problem with cloud-init.

However, when I deploy a vm with my CentOs 7 image (handly deployement using the same image, not by sahara), cloud-init manages to set hostname. Deployment settings seem to be the same for sahara-provisionned vm and manually-created vm.

Note : I'm using neutron private network, keypair, and public floating IPs.

Any idea ? What it does not work with sahara ?

Edit : When I disable namespace in sahara conf, it works but not for each vm. If I reboot vm that failed, it works ! May first boot is too long for cloud-init ? What should I do ?