-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fixes to adjust with latest ansible v2.16.3 #85
Fixes to adjust with latest ansible v2.16.3 #85
Conversation
8c3ad09
to
b933b22
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of adding version dependencies, couldn't we install jmespath using pip instead of the CentOS package ?
It is my guess that pip executable will also need to used accordingly with required Python version(pip3.11, pip3.12 etc). So its a choice between specifying ansible version and pip executable version. Let me verify that it is the case here. |
Ok. I think I got it confused. I'll check by replacing jmespath python module installation from RPM to pip with required versioned executable. |
4f80db3
to
bf0500d
Compare
ac4f9bf
to
e375047
Compare
/retest all |
I've manually adjusted required jobs to pick up samba-in-kubernetes/samba-centosci#54 for their execution. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit ugly but I don't see any other way to do that. Let's make it work for now.
Isn't playbooks/roles/setup.prep/tasks/centos.yml |
We discussed offline and decided to have |
e375047
to
5012d81
Compare
Very recently on CentOS Stream 8 ansible version got updated to v2.16.3 built with Python 3.12. Due to unavailability of python 3.12 module for jmespath playbook execution is expected to fail. Therefore switch the python module installation from RPMs to pip where it can be versioned. Signed-off-by: Anoop C S <[email protected]>
Recent update to ansible v2.16.3 broke[1] the promised action of first_found plugin to find files with relative paths when tasks are included from a different subdirectory other than where its main.yml is located. Thus we temporarily switch to use absolute paths wherever required until fix is available with an updated package. [1] ansible/ansible#82695 Signed-off-by: Anoop C S <[email protected]>
5012d81
to
5150ec9
Compare
🎉 All dependencies have been resolved ! |
Very recently on CentOS Stream 8 ansible version got updated to v2.16.3 built with Python 3.12. Due to unavailability of python 3.12 module for jmespath playbook execution is expected to fail. Therefore switch the python module installation from RPMs to pip where it can be versioned.
Additionally due to a regression in
first_found
plugin we switch to absolute paths wherever required to find OS specific files. See ansible/ansible#82695 for more details.depends on samba-in-kubernetes/samba-centosci#54