From 24f8ef65d04e4acfb6df15d3544d08041b0a422b Mon Sep 17 00:00:00 2001 From: Dougal Matthews Date: Mon, 1 Oct 2018 10:56:08 +0100 Subject: [PATCH] Add a release note for Ic98e2db02abd8483591756d73e06784cc2e9cbe3 Change-Id: I484b47f9e0d94c37079961d18061e2e9e121af92 (cherry picked from commit f0b49a82b4c4d00961f051f69470325c8c481999) --- .../cleanup-rpc-cleints-transport-eaa90fef070b81fd.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 releasenotes/notes/cleanup-rpc-cleints-transport-eaa90fef070b81fd.yaml diff --git a/releasenotes/notes/cleanup-rpc-cleints-transport-eaa90fef070b81fd.yaml b/releasenotes/notes/cleanup-rpc-cleints-transport-eaa90fef070b81fd.yaml new file mode 100644 index 000000000..94ade332d --- /dev/null +++ b/releasenotes/notes/cleanup-rpc-cleints-transport-eaa90fef070b81fd.yaml @@ -0,0 +1,8 @@ +--- +fixes: + - | + Cleanup transports along RPC clients. Fixed 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 triggers. If a + SIGUP signal happens after, the child inherits the connection, but it's + non-functional.