Comment 7 for bug 1752932

>> I can't seem to test it on my machine, because of credentials (no secrets, nor access to the remote machine). Running bootstrap aio and then copying the user variables, env.d, and group vars fail on the proxy part of the user_variables.yml, which is expected, so i removed that part of your user_variables file.

ahould be able to clone repo, cp -R openstack_deploy /etc, rm /etc/openstack_deploy/user_secrets.yml... user_secrets is not needed to repro this and its the only vaulted file.

>> Anyway... With all that set, it proves the user_variables, env.d, groups_vars, are not causing this.
It's definitely something that must appear from the inventory/remote node.

yep.. this is reproducible without any of the user_* files present

>> I'd be curious to know if ansible localhost -m debug -a msg="{{ hostvars['lsn-mc1023'] }}" -vvvv has the same problem.

it does.
py3 queens env: http://paste.openstack.org/raw/700925/
py2 queens env: http://paste.openstack.org/raw/700927/

>> Also it would be interesting to know why we're using python3 on the node.

We've been using py3 for the ansible-runtime venv for most of the last 2 (pike and queens) cycles: https://github.com/openstack/openstack-ansible/commit/5b9d96e75a0b290bb6c5e42a4c419cca78090ee9#diff-30c3701b5527d757251851f9253bbb3c

>> Could you also have a dump of your bootstrap-ansible script?
>> I have the impression we are doing something wrong with python3, and installing stuff that don't matter (with different requirements) using pip instead of pip3.

Full py3 run: http://paste.openstack.org/show/700932/
Full py2 run: http://paste.openstack.org/show/700935/