-
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-ssh 3005: no execution modules are available to any renderer #62636
Comments
This fixes it: #62635 |
The patch linked above does not fix this. |
As far as I can tell, this upstream bug broke our provisioning logic within Qubes OS, since we rely in a few places on Salt calls within Jinja syntax and suddenly started seeing similar errors after the 3005 update. Just a data point in case you're still assessing priority (for now downgrading Salt appears to resolve). |
Regression test for saltstack/salt#62636 and saltstack/salt#61083
This issue has been resolved and will be released in the next bugfix release, targeted soon. |
Should be released upstream soon, but since its impact lets "apply" it earlier.
Regression test for saltstack/salt#62636 and saltstack/salt#61083
Regression test for saltstack/salt#62636 and saltstack/salt#61083 (cherry picked from commit b3cb195)
I recently upgraded to 3005. None of the module functions are accessible under
__salt__
in thepyobjects
or in thejinja
renderer — I just get a traceback now.Pyobjects:
Jinja:
The text was updated successfully, but these errors were encountered: