Comment 9 for bug 1906566

I wasn't using the same venv, but /root/kolla-ansible/venv for kolla-ansible and /root/targethost/env for Ansible on "target".

Anyhow, paying attention to docs avoids the problems:

> Typically we will need to enable use of system site-packages from within this virtualenv, to support the use of modules such as yum, apt, and selinux, which are not available on PyPI.

> When executing kolla-ansible commands other than bootstrap-servers, the variable ansible_python_interpreter should be set to the python interpreter installed in virtualenv.

I was also mixing the `python3 -m venv /path/to/venv` example command for control host with creating venv on target (the latter is actually done by Ansible, not manually).

I think the issue may be closed.

Thanks