Cleanup transport along RPC clients
This fixes a bad weird condition in the API server related to
cron-triggers and SIGHUP. The parent API server creates a RPC connection
when creating workflows from cron. If a SIGUP signal happens after, the
child inherits the connection, but it's non-functional.
Change-Id: Ic98e2db02abd8483591756d73e06784cc2e9cbe3
Closes-Bug: #1789680
(cherry picked from commit 5c005a7926
)
This commit is contained in:
parent
24cb2daea6
commit
204e96e8fc
@ -51,6 +51,8 @@ def cleanup():
|
||||
_EXECUTOR_CLIENT = None
|
||||
_EVENT_ENGINE_CLIENT = None
|
||||
|
||||
base.cleanup()
|
||||
|
||||
|
||||
def get_engine_client():
|
||||
global _ENGINE_CLIENT
|
||||
|
Loading…
Reference in New Issue
Block a user