Comment 2 for bug 1763422

So really the only place we call config_template in a py3 context is during bootstrap hosts, and it exposes issues like we saw with yaml overrides last year:
https://github.com/openstack/openstack-ansible-plugins/commit/2a286fb0fb0b1fc8fab2126837600c1c70f4e8de
https://github.com/openstack/openstack-ansible-plugins/commit/2d1dd94264e9406c0d4109e5877a2eb0237e06c2

Seems we have similar breakages for py3 with INI templates that are exposed when config_overrides are provided. We don't see it in the gate because config_overrides dicts are always empty in the gate which means none of the config_template override features are exercised there.

It also appears the py3 non-voting test in the plugins repo does not fail when using ini w/ config_overrides, so that is something we'll need to address also. (Random recent merged patch test result to follow):
http://logs.openstack.org/45/557545/1/check/openstack-ansible-python3-ubuntu-xenial-nv/494991a/job-output.txt.gz

Since the integrated gate is not useful to test our plugins compatibility with py3, and since we rely on py3 compat to some extent in the integrated repo, we should aim to get this py3 test in the plugins repo working and voting asap.