Closed MarcFinetRtone closed 5 years ago
Do you think this is a bug in version
or in this role?
Do you think this is a bug in
version
or in this role?
I've no idea. The documentation for version()
is very small (https://docs.ansible.com/ansible/latest/user_guide/playbooks_tests.html). In fact, I'm surprised the existing code does not work. It's either:
version()
that changedansible_distribution_version
that changedI tried to google() for the same problem and didn't find anything conclusive. Other references:
On my debian stretch, the ansible_distribution_version is 9, not 9.0 nor 9.x. Moreover the version() filter returns False leading to set "ssh" instead of expected "sshd".
I have the same problem. The role worked perfectly until a few days ago on Debian 9.X
(I have been using it for more than a month).
I have not updated the role or Debian on which the role is executed, but recently I updated Ansible from version 2.7
to 2.8
.
I suspect that this error is related to Ansible 2.8
Correct, this is an error in Ansible 2.8.
The bugfix is coming
Fixed in #57
On my debian stretch, the
ansible_distribution_version
is9
, not9.0
nor9.x
. Moreover theversion()
filter returnsFalse
leading to set "ssh" instead of expected "sshd".On my local machine (debian 9):
On my remote machine:
The role I wrote to see
version()
in action:Output:
Ansible version: 2.8.0: