-
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
iptables states fail when state_aggregate option is enabled #53353
Comments
For reference - it doesn't look like I'm not sure what the real root cause is, that's creating the cyclical reference in the first place... In either case we should either be a) throwing a proper Salty exception when we detect a cyclical reference b) skipping recursing through the cycle or c) allow both options. |
FWIW I wasn't able to reproduce this in a docker container - a proper VM or something may be necessary. @dstoliker quick question:
If you remove |
@waynew, your hypothesis is correct. Removing the |
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. |
Thank you for updating this issue. It is no longer marked as stale. |
For future readers, we worked around this bug by patching our Beware that setting |
There appears to have been a regression at some point. I know it worked on some earlier versions of 2019.2.x and 3000.x, but in with any current versions now available in the repo, the same recursion error detailed above appears. Using the same configuration and test state above on a CentOS 7 test machine, the recursion error appears, and no changes are applied with these versions:
Version 3001 behaves a bit differently. It completes successfully, changes are applied, but does report errors to the CLI.
|
my mistake, the merged PR is from when we thought we fixed this and there is not a new PR to correct the regression, putting this back into Commit for Magnesium |
@dstoliker we didn't get to this in Magnesium, so I am putting it in Aluminium to get it addressed and assigned Shane to take a look now. |
Shane was able to get this in AL let me see when he can @twangboy |
@dstoliker looks like this might be something else and putting this work into |
Description of Issue
State files with iptables states will fail with a runtime error
RuntimeError: maximum recursion depth exceeded in cmp
when running Salt 2019.2 withstate_aggregate
enabled in/etc/salt/minion
.Setup
Enable
state_aggregate
in/etc/salt/minion
:Create a state file like this example:
Steps to Reproduce Issue
Apply the state file:
These go on repeating for quite a while...
... snip ...
Above state works fine if
state_aggregate
isFalse
. Same state also works fine if run on Salt 2018.3.x regardless ofstate_aggregate
setting in config.Versions Report
The text was updated successfully, but these errors were encountered: