Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I still consistently get the issue on a reconfigure or even a destroy/deploy using latest 6.0.0.0rc2 version and the additions in the above commit are present in my bootstrap.yml. This is on ubuntu 16.04 on the same server as the deployment. The mariadb container is running fine.

I have also tried using localhost or the server name explicitly (there was another page that hinted there might be an issue with unix sockets being in an unexpected location. However I have deployed OK with an earlier version of kolla-ansible

My hardware is not as fast as I would like and when doing a koll-ansible deploy with -vvv option piped out to a local file I did manage to get it successful just once but I cannot repeat it. Is there a timing dependency??

I still consistently get the issue on a reconfigure or even a destroy/deploy using latest 6.0.0.0rc2 version and the additions in the above commit in the other answer are present in my bootstrap.yml. This is on ubuntu 16.04 on the same server as the deployment. The mariadb container is running fine.

I have also tried using localhost or the server name explicitly (there was another page that hinted there might be an issue with unix sockets being in an unexpected location. However I have deployed OK with an earlier version of kolla-ansible

My hardware is not as fast as I would like and when doing a koll-ansible deploy with -vvv option piped out to a local file I did manage to get it successful just once but I cannot repeat it. Is there a timing dependency??