I have successfully tested the use of a virtualenv on the remote target hosts to work around this issue. This can be achieved by setting a host variable, ansible_python_interpreter, to a python interpreter installed in a virtualenv. Because kolla-ansible uses some python modules which are not available via PyPI, such as apt, yum, and selinux, it is typically necessary to create the virtualenv with --system-site-packages.
Ideally some support is required for installing this virtualenv, and the logical place for that is the kolla-ansible bootstrap-servers command and the baremetal role. I will propose a change which I used to test this.
I have successfully tested the use of a virtualenv on the remote target hosts to work around this issue. This can be achieved by setting a host variable, ansible_ python_ interpreter, to a python interpreter installed in a virtualenv. Because kolla-ansible uses some python modules which are not available via PyPI, such as apt, yum, and selinux, it is typically necessary to create the virtualenv with --system- site-packages.
Ideally some support is required for installing this virtualenv, and the logical place for that is the kolla-ansible bootstrap-servers command and the baremetal role. I will propose a change which I used to test this.