-
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
possible [BUG]? 3000.9 cmd.run with test=true does not trigger watch/watch_in #60284
Comments
@dmurphy18 looks similar, but when I test PR #60150 using |
For adjusted foo.sls where /dog/kat already exists
and PID's before and after
The service may or may not be restarted, depending on the state of systemd and other items in the system.
to
|
From Slack conversion with @onmeac
|
The PR's #61019 and #61019, back to square one. With Salt 3004 for Master and Minion and using the provided test case, the following is produced.
And with Master and Minion off the current Master branch(2022-02-14 and pip installed)
Closing this issue since the output for the postfix has been address from what it was. Given the long arguments in the threads for the above PR's and their associated issues, and not wanting to rehash here, as to what should be reflected with test=True, going to close this issue, as believe it has been adequately addressed by the other PR's. Please reopen if you feel this is unsatisfactory but provide knew information as to why the above PR's do not adequately respond to your concerns. Note: The above changes should be available with the next major release of Salt, Phosphorous. |
Description
A
cmd.run
duringtest=true
that "would have been executed" does not have any changes, obviously becuase the cmd hasn't run yet.Because
cmd.run
has no changes,service.running
that has a watch on thatcmd.run
duringtest=true
does not mention "Service is set to be restarted".There is logic already present for
cmd.run
, e.g. unless/onlyif, which helps to determine ifcmd.run
is going to something.Setup
foo.sls (simplified example)
Steps to Reproduce the behavior
echo something > /test
salt-call state.apply foo test=true
service_test not mentioning going to restartsalt-call state.apply foo
service_test restartedExpected behavior
service_test should mention: "Service is set to be restarted" during
test=true
Versions Report
salt --versions-report
The text was updated successfully, but these errors were encountered: