Comment 2 for bug 1637509

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

The issue appears to relate to the different python versions between the platforms.

Options off the cuff:

1. Make the repo build process be both multi-architecture and multi-platform. The multi-arch works by requiring one repo container per architecture. We could extend this to be multi-distro too so that you have to have one container for each distro you're running and it will create wheels for each of them. I don't know if trusty and xenial wheels will overwrite each other though. According to https://www.python.org/dev/peps/pep-0491/ is may not be granular enough to deal with the difference of version in the name to prevent a clash.

2. Re-initialise the python binaries in the venv if the repo_all[0] and the current host differ in python versions.

3. Override the venv download URL to something not accessible from the host so that the host in question falls back to building its own venv. https://github.com/openstack/openstack-ansible/blob/master/playbooks/os-nova-install.yml#L157