Skip to content
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

Action-Aliases salt-local state.highstate doesn't apply highstate #15

Open
nzlosh opened this issue Dec 11, 2019 · 0 comments
Open

Action-Aliases salt-local state.highstate doesn't apply highstate #15

nzlosh opened this issue Dec 11, 2019 · 0 comments

Comments

@nzlosh
Copy link
Contributor

nzlosh commented Dec 11, 2019

When the salt.local action is called from the command line providing module=state.highstate and target, the high state is applied to the target machine. If the action is trigger via the action-alias, the result appears to apply the configuration changes but none are observred on the target machine. It seems like it's running with test=true.

salt.local from action-alias

id: 5defab2838b7e592a6f1332c
status: succeeded (5s elapsed)
parameters:
  args:
  - '[]'
  module: state.highstate
  target: automate*
result:
  exit_code: 0
  result:

salt.local from cli

id: 5df0064c38b7e592a6f13347
status: succeeded (5s elapsed)
parameters:
  module: state.highstate
  target: automate*
result:
  exit_code: 0
  result:

The only difference I can see between the 2 calls is that arg parameter is passed an empty list. This behaviour has been observed using salt-2018.3.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant