RBD: cannot reduce max clone depth setting
Bug #1901241 reported by
David Hill
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Brian Rosmaita |
Bug Description
RBD: cannot reduce max clone depth setting as cinder-volume raises an Exception and bails out. An operator cannot change max clone depth value from a higher value to a lower value but can from a lower value ot a higher value.
Changed in cinder: | |
assignee: | nobody → David Hill (david-hill-ubisoft) |
status: | New → In Progress |
Changed in cinder: | |
assignee: | David Hill (david-hill-ubisoft) → Eric Harney (eharney) |
Changed in cinder: | |
assignee: | Eric Harney (eharney) → Brian Rosmaita (brian-rosmaita) |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/759328 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=8d8d242c392 4037e6774a681ef abce4893a26646
Committed: https:/
Submitter: Zuul
Branch: master
commit 8d8d242c3924037 e6774a681efabce 4893a26646
Author: David Hill <email address hidden>
Date: Thu Oct 22 18:56:19 2020 -0400
Do not fail when depth is greater than rbd_max_clone_depth
Removed a sanity check in the code that raised an exception max_clone_ depth config value. A consequence of this
if the clone depth of a volume to be cloned exceeded the
rbd_
check was that if an operator lowered the value, volumes
whose clone depth was greater than the new value (as would
be allowed by the previous, higher setting) could no longer
be cloned.
Change-Id: I8c445058a25c2e ca2fda91bdeb6be fedae34ccf2
Closes-bug: #1901241