Do not lookup reverse dns with salt-ssh #58163
Merged
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?
Salt-SSH was using the reverse DNS for the target. This PR ensures we do not check the reverse DNS and only use the target the user defined.
What issues does this PR fix or reference?
Fixes: #49840
Previous Behavior
salt-ssh target used the reverse DNS
As you can see we target 127.0.0.1 but it returns localhost as the target name
New Behavior
salt-ssh does not use reverse DNS and uses the target the user sets.
the target stays the same (127.0.0.1)
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
Yes