From 4e4ec2d8bd98dc91dc772b706f312321531b1db2 Mon Sep 17 00:00:00 2001 From: Roman Podoliaka Date: Fri, 1 Jul 2016 19:27:11 +0300 Subject: [PATCH] release notes: mention changes in wrap_db_retry() Just in case mention the changes done in CR #318135, so that people are aware of those (although, we've double checked everyone passes the argument value explicitly now and that's the only reason the decorator actually performs any retries in downstreams). Change-Id: I263b2078535a3f06461e8905003b484a38d05f08 --- releasenotes/notes/wrap_db_retry-34c7ff2d82afa3f5.yaml | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 releasenotes/notes/wrap_db_retry-34c7ff2d82afa3f5.yaml diff --git a/releasenotes/notes/wrap_db_retry-34c7ff2d82afa3f5.yaml b/releasenotes/notes/wrap_db_retry-34c7ff2d82afa3f5.yaml new file mode 100644 index 00000000..1e3b4348 --- /dev/null +++ b/releasenotes/notes/wrap_db_retry-34c7ff2d82afa3f5.yaml @@ -0,0 +1,6 @@ +--- +fixes: + - Decorator ``oslo_db.api.wrap_db_retry`` now defaults to 10 retries. + Previously the number of attempts was 0, and users had to explicitly + pass ``max_retry_interval`` value greater than 0 to actually enable + retries on errors.