fix: ensure ansible_python_interpreter is set in all playbook runs#259
Merged
tropicrainforest merged 1 commit intomainfrom Apr 7, 2026
Merged
Conversation
antarcticrainforest
approved these changes
Mar 26, 2026
Contributor
antarcticrainforest
left a comment
antarcticrainforest
left a comment
There was a problem hiding this comment.
LGTM!
But looking at this I doubt it solves the problem - because my understanding from the old code is that it shouldn't have bin there in the first place.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes
ansible_python_interpreternot being passed to the version check playbook, causing Ansible to fall back to auto-discovery and pick up the default system Python on managed nodes. On hosts like levante4.dkrz.de the system Python is older than 3.8, which is incompatible with ansible-core ≥ 2.17 module syntax and breaks the deployment.A helper is introduced so that both the main deployment and version check code paths always set the interpreter consistently.
An alternative would be to exclude
corefrom this list, but that only masks the symptom; any new service added in the future would face the same issue again.