Closed lae closed 6 years ago
For anyone affected by this, my current workaround is to blacklist 2.5.1 in the environment, e.g.:
env:
- ANSIBLE_VERSION='ansible>=2.5.0,<2.6.0,!=2.5.1' # 2.5.x
- LXC_DISTRO=debian LXC_RELEASE=jessie ANSIBLE_VERSION='ansible!=2.5.1'
Hi,
Thanks for the workaround. But, to my humble opinion, a fix would be appreciated by the community. I use ubuntu 18.04 LTS and I need to upgrade to Ansible 2.6 as a workaround.
Thanks a lot
@jbroq This was supposed to be resolved in https://github.com/lae/ansible-role-travis-lxc/commit/95b006e3213f465c70b58b0221c45f92ae48faaa without a workaround. That said, 2.5.1 is no longer current 2.5.x and the original issue was fixed in 2.5.2 (in which case, you shouldn't be using 2.5.1 anymore to be honest).
If you're having an issue, it would help to provide an example.
This issue wasn't identified from tests in this role since we only test with one container, but it's very apparent in the roles using it to test:
lxc_hosts
is failing to be populated correctly, which causes containers to not be configured thoroughly and cascades into the playbooks not being able to reach the containers.Opened issue here: https://github.com/ansible/ansible/issues/38991
It appears to be resolved in
devel
and slated for 2.5.2 release (not sure when since 2.5.1 was just released, though...): https://github.com/ansible/ansible/pull/38302