summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoman Podoliaka <rpodolyaka@mirantis.com>2016-07-01 19:27:11 +0300
committerRoman Podoliaka <rpodolyaka@mirantis.com>2016-07-04 13:38:25 +0300
commit4e4ec2d8bd98dc91dc772b706f312321531b1db2 (patch)
tree16b76a4ba2e4a86572ce5b713c478d25e33cd4f1
parent1d7e7e453bd3520a0e2772a094a6ce70ad1fd342 (diff)
downloadoslo-db-4e4ec2d8bd98dc91dc772b706f312321531b1db2.tar.gz
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
-rw-r--r--releasenotes/notes/wrap_db_retry-34c7ff2d82afa3f5.yaml6
1 files changed, 6 insertions, 0 deletions
diff --git a/releasenotes/notes/wrap_db_retry-34c7ff2d82afa3f5.yaml b/releasenotes/notes/wrap_db_retry-34c7ff2d82afa3f5.yaml
new file mode 100644
index 0000000..1e3b434
--- /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.