Skip to content
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

Move to ansible 3.x #7671

Closed
cristicalin opened this issue Jun 1, 2021 · 4 comments · Fixed by #7672
Closed

Move to ansible 3.x #7671

cristicalin opened this issue Jun 1, 2021 · 4 comments · Fixed by #7672
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@cristicalin
Copy link
Contributor

What would you like to be added:
Following the merge of #7600 and subsequent release of our 2.16.0 version, I propose we move to ansible-base 2.10.x which is included in the new upstream ansible 3.x branch as the default ansible version of kubespray.

Why is this needed:
We should try to keep up with ansible evolution and adapt our code to use the new versions. This change would allow us to start migrating our code to use fully qualified module names.

@cristicalin cristicalin added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 1, 2021
@cristicalin
Copy link
Contributor Author

Seems that flipping the default ansible is a lot more headache.

Current outstanding issues:

@cristicalin
Copy link
Contributor Author

Mitogen tests are failing due to mitogen 0.2.x not being supported with Ansible 2.10. We need to wait for version 0.3.0 to be released.

See https://mitogen.networkgenomics.com/changelog.html

@cristicalin
Copy link
Contributor Author

Linked issue #7689

@cristicalin
Copy link
Contributor Author

cristicalin commented Jun 14, 2021

ansible/ansible#74850 was merged and will probably make it into the next tagged 2.10.x release (2.10.11).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant