Task to fail if ansible_min_version isn't met

[gundalow]

At somepoint the Roles will use Ansible features that are only in certain releases, ensure that the end user is running the correct version of Ansible.

Read ansible_min_version from meta/main.yml and fail the playbook if
that version of Ansible (or higher) isn't being used.

Use fail, rather than assert to avoid noisy error message.

Ansible 2.5

TASK [ansible-network.network-engine : read ansible_min_version from meta data] **************************************************************************
ok: [localhost]

TASK [ansible-network.network-engine : validate minimum Ansible version] *********************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "This role requires Ansible 2.6 or higher. You are currently running Ansible 2.5.2."}

PLAY RECAP ***********************************************************************************************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=1   

Ansible 2.6

TASK [ansible-network.network-engine : read ansible_min_version from meta data] ***
ok: [localhost]

TASK [ansible-network.network-engine : validate minimum Ansible version] *******
skipping: [localhost]

TASK [ansible-network.network-engine : validate connection is network_cli] *****

... Play continues

[gundalow]

If we are happy with this we should backport into stable-2.5

[gundalow]

Should this go into a dedicated tasks/validate.yaml which all other tasks include?

[trishnaguha]

@gundalow see #131. You can add this validation in main.yaml instead as it is entrypoint, so it will run for plugins and modules also.

[privateip]

I have a slightly different pattern that makes this work a little more seamlessly within the roles. Take a look at the following two links:

https://github.com/ansible-network/arista_eos/blob/devel/tasks/load_config.yaml#L3
https://github.com/ansible-network/arista_eos/blob/devel/includes/init.yaml

The above pattern creates an init set of tasks where we can centrally handle all role validation instead of having to manage individual ones and make sure they are propagated to every role, every time.

[trishnaguha]

+1

[softwarefactory-project-zuul]

Build succeeded.

• ansible-test-sanity : SUCCESS in 5m 10s
• ansible-role-tests-devel-py2 : SUCCESS in 1m 33s
• ansible-role-tests-2.6-py2 : SUCCESS in 1m 36s
• ansible-role-tests-2.6-py3 : SUCCESS in 1m 35s

[softwarefactory-project-zuul]

Build succeeded (gate pipeline).

• ansible-test-sanity : SUCCESS in 5m 17s
• ansible-role-tests-devel-py2 : SUCCESS in 1m 42s
• ansible-role-tests-2.6-py2 : SUCCESS in 1m 33s
• ansible-role-tests-2.6-py3 : SUCCESS in 1m 29s