reset multiplexer only at connection failure #83851
Open
+5
−5
Conversation
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
ansibot
added
feature
Member
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
s-hertel
removed
the
needs_triage
ansibot
added
the
stale_ci
ansibot
added
the
stale_pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
SUMMARY
When using
wait_for_connectionmodule at the beginning of every Ansible run, it resets the multiplexed connection every time. It's not nice because triggers extra connection tossh-agentwhich can be avoidedISSUE TYPE
ADDITIONAL INFORMATION
The patch makes
wait_for_connectionmodule reset the multiplexed connection only at failure for the next try. Successful connections will use existing multiplexed connection