[master] Do not make Salt CLI to crash when there are IPv6 established connections #55583
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 ports #52888 to master branch, and fixes an issue at 2019.2.x release.
What does this PR do?
This PR fixes an issue in
utils/network.py
which is making the Salt CLI to crash when some of the targeted minions cannot be reached.Currently, the
_netlink_tool_remote_on
function is not taking care of possible IPv6 entries returned byss -ant
.When there are minions that did not response on time, then this code is executed. In case the underlying call to
ss -ant
returns an IPv6 entry, this would make the Salt CLI to crash while trying to parse the host/port.Previous Behavior
New Behavior
Tests written?
Yes
Commits signed with GPG?
Yes
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.