-
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
Jinja condition is not being evaluated correctly in salt-ssh minion #56030
Comments
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. |
This problem still exists and I would appreciate it if someone from the salt team could provide some information about the possible fix. |
I'm also interested in a fix. The root of the problem seems to be here: https://github.com/saltstack/salt/blob/master/salt/client/ssh/wrapper/__init__.py#L66-L99 According to Python docs, However, adding @Ch3LL Maybe you can shed some light on this issue (and also reopen it)? |
@admd The workaround is to use the following syntax:
|
Bad bot! |
Thank you for updating this issue. It is no longer marked as stale. |
ive added this issue to my backlog to take a look at, time permitting |
Description of Issue
I need to check if salt module exist before executing it. So I have a Jinja condition in statefile but it is not working on salt-ssh minion.
Setup
Above excerpt correctly returns nothing when executed on a regular minion and
network.fqdns
module is not available. But when executed on a salt-ssh minion, it returns.which is not what I expect.
Steps to Reproduce Issue
Execute a state with a condition like above, once on a regular minion and once on salt-ssh minion. Regular minion will return nothing in case module is not there while salt-ssh minions will return the result as mentioned above.
Versions Report
The text was updated successfully, but these errors were encountered: