-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documented requirements are out of date #1641
Comments
I would tend to say it should still work with 2.9, what errors did you get? |
This was the main problem
There was also an issue with the AlmaLinux instances, I think Ansible was not correctly reporting it as a RedHat derivative. This was using 2.9.6. |
Would you have the time to try with a "less-ancient" 2.9 version? |
Was just doing that... It works with 2.9.20. Not sure if that warrants an update to the readme? It cost me a whole morning trying to debug it. |
Yeah, that sounds like a valuable update! We started using collections at some point, and there were still bugs in that regard in early versions if 2.9, so it might very well be what you've been seeing |
The readme specifies Ansible 2.9+ but that seems to no longer be sufficient due to multiple errors in the playbooks.
2.13.7 worked for me, but a lower version may also work?
The text was updated successfully, but these errors were encountered: