From fd5db96e85712aed059376fa5c242773ac8ba581 Mon Sep 17 00:00:00 2001 From: Sharat Sharma Date: Tue, 29 Nov 2016 16:05:57 +0530 Subject: [PATCH] Added releasenote for retry policy update https://review.openstack.org/#/c/383617/ updates the retry policy and is a huge change for some of the workflows. Hence, adding a releasenote. Change-Id: I86d88d80c3fbcba098d41671f3131f68d10fac03 --- .../notes/update-retry-policy-fb5e73ce717ed066.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 releasenotes/notes/update-retry-policy-fb5e73ce717ed066.yaml diff --git a/releasenotes/notes/update-retry-policy-fb5e73ce717ed066.yaml b/releasenotes/notes/update-retry-policy-fb5e73ce717ed066.yaml new file mode 100644 index 00000000..95ba7813 --- /dev/null +++ b/releasenotes/notes/update-retry-policy-fb5e73ce717ed066.yaml @@ -0,0 +1,8 @@ +--- +critical: + - Due to bug https://bugs.launchpad.net/mistral/+bug/1631140, + Mistral was not considering retry with value 1. After this bug is + fixed, Mistral now considers count value 1 as a value for retry. + - Mistral does not consider the initial task run as a retry but + only considers the retry value after the failure of initial task + execution.