[docker-wait-any] End child threads when main thread is signalled to end #10812
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.
Why I did it
This is to fix a bug in
docker-wait-any
script which leads to Exceptions during shutdown path for services.Reason for this error:
docker-wait-any
as part of systemctl wait function.docker-wait-any
creates different threads that wait as long as dependent services are running.docker_client
instance which is owned by main thread.docker_client
instance, but the child threads are still running and use the samedocker_client
instance.Error trace shows that the error is always originated during chilkd thread accessing
docker_client
, which is being freed up by main thread:Instance 1:
Instance 2:
Instance 3:
How I did it
Child thread should break out of infinite loop after signaling main thread to unblock and exit.
How to verify it
Tried multiple times on physical testbed and issue is not seen with this fix,
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)