-
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
[ERROR ] Got a bad pillar from master, type str, expecting dict: #27792
Comments
@tiger-seo, thanks for the report. Is it possible for you to provide a minimal test case to demonstrate this problem? |
I see this too in the minion logs but I have no idea when it started or what caused it.... which I realize isn't very useful. This is with 2015.5.2 minions. |
@jfindlay -- Update: I figured it out.... I was not out of disk space but the master cache had exhausted 100% of the inodes for the /var filesystem. Solution:
|
Excellent, thanks @sjwoodr. I have a suspicion this occult error message may be masking more than one problem. At least in the case you have found, I think we can handle and message a more useful error. |
@jfindlay i don't have a test case, because in my case on both our environments (stage and prod) the only needed step is to upgrade to 2015.5.5 |
|
@tiger-seo, any more information you can provide about your pillar setup or salt setup that you think may be related to this would be helpful, thanks. |
@jfindlay I see something similar and this is what the masters log outputs 2015-11-03 12:40:02,229 [salt.master ][ERROR ][10272] Error in function _pillar:
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/salt/master.py", line 1460, in run_func
ret = getattr(self, func)(load)
File "/usr/lib/python2.6/site-packages/salt/master.py", line 1236, in _pillar
'pillar': data})
File "/usr/lib/python2.6/site-packages/salt/payload.py", line 122, in dumps
except (OverflowError, msgpack.exceptions.PackValueError):
AttributeError: 'module' object has no attribute 'exceptions' |
@brucemartins, this is a separate issue that has been fixed in #26714. |
@jfindlay please help me to provide you more information, because I have no idea |
Btw, supposedly, this error doesn't appear if I run state without pillar being used |
@tiger-seo, have you investigated @sjwoodr suggestions? |
@jfindlay as i sad previously, the same problem appeared on both our environments, for sure it was not about disk free space or inodes ;) |
I'm seeing this pop up on 2015.5.5 master/2015.5.5 minions if my pillar YAML contains a sequence of mappings. This is consistent and is affecting pillars that have been in use successfully for some time, which pass YAML lint. Here's an example:
UPDATE: Also affects a 2015.5.5 master/2015.8.1 minion combo. |
@kevins9 Using that pillar on a 2015.5 master/minion combo, I don't see any issues running
|
Master:
Minion 1:
Minion 2:
|
Hmm, still not able to reproduce this. Anything in debug logs on master/minion? |
On master, some instances of this in /var/log/salt/master:
Appears relevant. |
I'd noticed the same issue on our minions when we had the salt master cache pillar data to memory:
Using the default disk backend addressed the problem. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
after upgrading to 2015.5.5 got this error:
[ERROR ] Got a bad pillar from master, type str, expecting dict:
on 2015.5.3 it works as expected
The text was updated successfully, but these errors were encountered: