Join GitHub today
state.highstate error with require_in: sls: #47182
Description of Issue/Question
(followed by the complete state.highstate docs).
I found that when I removed the "require_in" block of something like
the error no longer appears. The same states worked fine in Salt 2017.x.x
The closest Issue I found is #22852, but that's supposed to be fixed. In either case, an error message pointing to the exact location would be nice (I had to "bisect" the state tree down to the exact location).
In the minion log file (level: trace), I found this Traceback:
Steps to Reproduce Issue
I'm having a hard time replicating this. Here is my test case:
Can you share your slsfile1 and slsfile2?
Indeed, the "slsfile1" and "slsfile2" again include and depend on other state files, the whole tree is quite deep, and sadly contains loads of stuff I am not allowed to disclose here :(
My colleague "fixed" it in the meantime by replacing the "require_in: sls" with "require:" in the deeper sls files.
Might there be a "nesting depth" limitation to require_in?
Out of curiosity, we reverted to the failing tree today.
We discovered that in another state, a previous include was excluded. After removing the exclude, it works, too:
Excluding the SLS
referenced this issue
May 16, 2018
This should reproduce the error referenced in the OP (though on 2017.7 it will mention
However, when checking out my PR locally and running it against that branch, the state.apply should run as expected.