salt.states.service
: detect that service failed to start/stop
#36607
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
It checks if service was successfully started up using
service.running
state or stopped (killed) usingservice.dead
state and makes Salt reportFalse
if desired result wasn't achieved.What issues does this PR fix or reference?
It fixes issues #16677 #33540
Previous Behavior
Example of weird side effects
Service is down:
This is an attempt to start the service:
But, because of bad config file or missed deps, the service actually failed to start:
Unexpectedly, Salt thinks that the service is up and running:
New Behavior
Salt is able to detect that starting/stopping the service has been failed and outputs correct results.
Tests written?
Added negative test case to the
test_running
test in theunit.states.service_test
module.Altered
test_dead
test:service.status
output: return second statusFalse
(after callingservice.stop
in the state module).service.stop
does not really stop the service.