From 204e96e8fc9c093f7468387bbda996d257a03be2 Mon Sep 17 00:00:00 2001
From: Thomas Herve <therve@redhat.com>
Date: Thu, 27 Sep 2018 11:45:42 +0200
Subject: [PATCH] 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 5c005a7926060b6898b536962d2e88ea922f1a32)
---
 mistral/rpc/clients.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/mistral/rpc/clients.py b/mistral/rpc/clients.py
index 865936c0a..73df86d76 100644
--- a/mistral/rpc/clients.py
+++ b/mistral/rpc/clients.py
@@ -51,6 +51,8 @@ def cleanup():
     _EXECUTOR_CLIENT = None
     _EVENT_ENGINE_CLIENT = None
 
+    base.cleanup()
+
 
 def get_engine_client():
     global _ENGINE_CLIENT