Fix salt-ssh not detecting platform-python
as a valid interpreter on EL8
#62236
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.
What does this PR do?
This PR adds an additional (this time absolute) python path to salt-ssh's
/bin/sh
shim, to support deployments where the available interpreter is EL'splatform-python
(and thus mimic thesalt
RPM package behaviour).This is a naive fix, I've originally thought about being able to use
--python3-bin
to steer salt-ssh into using the proper remote python, thus leaving theplatform-python
shenanigans to the user and their configuration choices, but that argument doesn't seem to be actually used bysalt-ssh
and my knowledge of the codebase isn't good enough to implement that change.What issues does this PR fix or reference?
Fixes: #62235
Previous Behavior
salt-ssh
would complain about Python 3 not being installed on a remote EL8 target even ifsalt
is installed on the target.New Behavior
salt-ssh
finds the/usr/libexec/platform-python
interpreter as an ultimate fallback to other more common python paths.Merge requirements satisfied?
Commits signed with GPG?
Yes