Open rajan-mis opened 4 years ago
@digvijay2016 Thanks
@digvijay2016 Thanks
We are seeing our playbook failure on ansible 2.4.2.0
@rajan-mis Instead of putting this requirement into the README, can we put this as an assert directly into the code? Thanks.
@mamuthiah Yes we can do that. thanks
I recommend both: prerequisite section in README and check in code
I'm torn here, i understand why we would want to put a pre-req on the minimum, but are we actually going to be continually testing with that minimum version to validate that it holds true... otherwise we would never know when we started using a module that isn't provided at that min version -- until someone reports it.
I have seen multiple failure with ansible version less than 2.7 . The same failure is happening on ubuntu and sles when i was doing unit testing of ubuntu and sles ansible code . I already implemented this validation and planning to create PR.
Hit this on RHEL7.8 node. It appears that the Red Hat extras repo for RHEL7.x only goes up to ansible 2.4.2.0: https://access.redhat.com/downloads/content/rhel---7/x86_64/3030/ansible/2.4.2.0-2.el7/noarch/fd431d51/package
This would imply any RHEL7.x nodes to install ansible from some other location.
Marking this as must fix:
Re.: 3. Query underlying ansible version (and if it's installed) during prechecks
Ansible Galaxy has the concept of role metadata (defined in meta/main.yml
), which also includes a min_ansible_version
. Running ansible-galaxy install
without the required version of Ansible will fail with an appropriate message.
One advantage of distributing the code through Galaxy... #106
Needs to add minimum supported Ansible version in the README