-
Notifications
You must be signed in to change notification settings - Fork 41
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
re-enable proxy service fails on execstart integration test #627
Conversation
28c9d13
to
00fa431
Compare
tests/tests/tier0/proxy-service-fails-on-execstart/test_proxy_service_fails_on_execstart.py
Outdated
Show resolved
Hide resolved
8aee893
to
6849584
Compare
Actually, I wonder if this is the right approach.
|
Another option is to add the kill signal to SuccessExitStatus= |
34effde
to
c8e960c
Compare
c8e960c
to
a3dc382
Compare
Signed-off-by: Michael Engel <[email protected]>
By using ExecStop= instead of ExecStart= a race condition is avoided that leads systemd to send a SIGTERM signal to the dep service, resulting in it being in a failed state. Signed-off-by: Michael Engel <[email protected]>
a3dc382
to
987d0bd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes: #320
This PR re-enables the - currently - skipped integration test for the proxy service where the
ExecStart
returns exit code 1.Running it locally a few times it works fine, so lets enable it again and see if the flakiness is gone.