From f93930bcb4411e58fa15c61d84d9ddddbdb4edd0 Mon Sep 17 00:00:00 2001 From: Michal Gershenzon Date: Tue, 15 Dec 2015 13:56:12 +0000 Subject: [PATCH] Add releatenote for fix execution saved in wrong tenant Change-Id: I4443481743e4b74091e2e0aea608b5c872a3da4b Related-Bug: 1521802 --- ...changing-context-in-delayed-calls-78d8e9a622fe3fe9.yaml | 7 +++++++ ...isolation-level-to-read-committed-7080833ad284b901.yaml | 4 ++-- 2 files changed, 9 insertions(+), 2 deletions(-) create mode 100644 releasenotes/notes/changing-context-in-delayed-calls-78d8e9a622fe3fe9.yaml diff --git a/releasenotes/notes/changing-context-in-delayed-calls-78d8e9a622fe3fe9.yaml b/releasenotes/notes/changing-context-in-delayed-calls-78d8e9a622fe3fe9.yaml new file mode 100644 index 000000000..f9e1eb6a1 --- /dev/null +++ b/releasenotes/notes/changing-context-in-delayed-calls-78d8e9a622fe3fe9.yaml @@ -0,0 +1,7 @@ +--- +security: + - > + [`bug 1521802 `_] + Fixing the problem that sometimes sub-workflow executions were run/saved + under the wrong tenant in cron trigger periodic task in multi-tenancy + deployment. diff --git a/releasenotes/notes/changing-isolation-level-to-read-committed-7080833ad284b901.yaml b/releasenotes/notes/changing-isolation-level-to-read-committed-7080833ad284b901.yaml index f8359f035..a766d3d7b 100644 --- a/releasenotes/notes/changing-isolation-level-to-read-committed-7080833ad284b901.yaml +++ b/releasenotes/notes/changing-isolation-level-to-read-committed-7080833ad284b901.yaml @@ -1,8 +1,8 @@ --- fixes: - | - [`bug 1518012 `_] - [`bug 1513456 `_] + [`bug 1518012 `_] + [`bug 1513456 `_] Fix concurrency issues by using READ_COMMITTED