[2016.3] Fix when targeting via pillar with Salt syndic #39145
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?
Fixing a weird edge case when using salt syndics and targetting via pillar. Without this fix the master of masters ends up in an infinite loop since the data returned from the minions is differently structured than if a sync was not in use.
What issues does this PR fix or reference?
N/A
Previous Behavior
When using a Salt syndic setup and targeting minions by Pillar values from the master of masters, the process would end up in an infinite loop since the data returned from the minions was different than what the previous logic was expected.
New Behavior
Adds an additional case looking for empty return data to allow the processes to properly exit once the minions have returned.
Tests written?
No
Please review Salt's Contributing Guide for best practices.