Ask Your Question

flashydave's profile - activity

2018-05-04 10:29:05 -0500 answered a question kolla-ansible deploy fails on DB create/connect (which works manually from within containers)

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 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??

2018-04-11 05:23:22 -0500 received badge  Famous Question (source)
2018-04-11 05:23:22 -0500 received badge  Notable Question (source)
2018-03-16 04:20:37 -0500 received badge  Popular Question (source)
2018-03-08 23:13:34 -0500 received badge  Student (source)
2018-03-05 11:04:15 -0500 asked a question kolla-ansible AIO ubuntu 16.04.3 QuickStart Install fails

I have been following the https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html (QuickStart Guide) with bare metal machines (and tried with some VM's) but despite many attempts I end up failing with the prechecks stage with

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: load_config() got an unexpected keyword argument 'config_dict'

It always occurs with the "Get container facts" step and usually TASK haproxy (Although it will fail on others later with the same error if you disable haproxy in globals.yml)

I have seen google references to compatibility issues with a variety of python libs recently (eg docker-py) but despite trying many of the possible fix attempts by downgrading the libraries I have not found a cure.

I have tried with/without a virtualenv and also tried both pike and source code variants.

I have also tried recipes at https://blog.inkubate.io/install-and-configure-openstack-ocata-with-kolla-as-a-standalone/ (inkubate) and at https://elatov.github.io/2018/01/openstack-ansible-and-kolla-on-ubuntu-1604/ (Karim's Blog).

I can make a little progress by downgrading docker-py from 3.1.0 to 2.7 for the prechecks which then pass but then deploy fails with unless I re-upgrade at which point I fall over during the pull stage with

AttributeError: 'module' object has no attribute 'get_config_header'

I can make progress on that if I pip uninstall docker-py and docker and then reinstall docker.

The deploy the falls over with errors with tasks failing with exit code=1 errors. If I repeat I can get progresiveluy further until eventually I become consistently stuck on

TASK [nova : Waiting for nova-compute service up] **************************************************
FAILED - RETRYING: Waiting for nova-compute service up (20 retries left).
...
FAILED - RETRYING: Waiting for nova-compute service up (1 retries left).
fatal: [localhost -> localhost]: FAILED! => {"attempts": 20, "changed": false, "cmd": ["docker", "exec", "kolla_toolbox", "openstack", "--os-interface", "internal", "--os-auth-url", "http://10.10.66.138:35357", "--os-identity-api-version", "3", "--os-project-domain-name", "default", "--os-tenant-name", "admin", "--os-username", "admin", "--os-password", "CoBPkDubdad0pRnUousJ1WNqtoQC2uIcDv8h3wt6", "--os-user-domain-name", "default", "compute", "service", "list", "-f", "json", "--service", "nova-compute"], "delta": "0:00:01.710048", "end": "2018-03-01 23:30:10.155493", "rc": 0, "start": "2018-03-01 23:30:08.445445", "stderr": "", "stderr_lines": [], "stdout": "[]", "stdout_lines": ["[]"]}

NO MORE HOSTS LEFT *********************************************************************************
        to retry, use: --limit @/usr/local/share/kolla-ansible/ansible/site.retry

In passing I also get earlier failures in the bootstrap-serves phase due to assumptions on the environment that are not true (requiring things like libvirtd installed and apparmor uninstalled) to pass that earlier step. Addressing those problems is relatively easy but makes me feel nervous that something isn't quite right with the environment dependencies even though it is a bare metal ubuntu server 16.04.3 install.

It looks like

  1. What is installed on ubuntu 16.04.3 has changed from 16.04
  2. docker-py has broken kolla-ansible when it moved to 3.x (API change?)
  3. docker-py tangles with docker itself (is docker-py now incorporated in docker?)

Please can someone define precisely what versions of the various tools DO work or can advise if there are errors in the ... (more)