-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Salt-minion pillars don't always refresh when they should #57180
Comments
I have seen this go both ways, false positives and false negatives.Which makes sense, because it is a caching problem. What makes it really dangerous is you could merge bad pillars, even with testing, because you got a false positive. |
@saltstack/team-core Any ideas on this one? |
I guess it is somehow related to #31907 .. I've the same issue with salt, edit a pillar, push to git, did a refresh (also restart the minion) but it sill doesn't show the (new) pillar value..
when I run the salt minion in debug mode I got this:
ask for pillars: (pillar.items)
ask for specific pillar:
actual behavior:
expected behavior:
|
Description
Salt-minion pillars don't always refresh when they should.
This is trickery to reproduce and seems to involve a race condition. The steps to reproduce have to be executed very fast.
I am pretty sure from testing that this is caused by changes in this PR, #54942 . I tried reverted the patches and the issue went away.
Steps to Reproduce the behavior
Locally:
Master:
Locally:
Master:
Expected behavior
The error on the first state.apply is expected. There is a pillar syntax error. The error on the second state.apply is not expected, because the syntax has been fixed. The git_pillar.update has pulled in new pillars as we can see by the True for salt-pillars. When we then refresh_pillar for that minion we get the correct result we should have gotten on the second state.apply.
Versions Report
The text was updated successfully, but these errors were encountered: