RBD driver ignores user-configured max-clone-depth
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Jon Bernard |
Bug Description
1. Interface cinder with rbd
2. Edit cinder config file with rbd entry:
[DEFAULT]
enabled_backends = rbd
glance_api_version = 2
[rbd]
volume_driver = cinder.
rbd_pool = volumes
rbd_ceph_conf = /etc/ceph/ceph.conf
rbd_flatten_
rbd_max_clone_depth = 2
rbd_store_
rados_connect_
rbd_user = cinder
rbd_secret_uuid = fb0040d4-
It would be simpler to try with rbd_max_clone_depth = 0
3. Restart cinder services
4. Now create three volumes from a source cinder volume by cloning the cinder volume using "cinder create --source-volid"
5. Check the ceph cluster for info on all the cinder volumes created in step#3
"rbd info volumes/volume-id"
Actual results:
After creating three cloned cinder volumes, the subsequent rbd volumes are still rbd clones and not flattened volumes.
Expected results:
The subsequent rbd volumes should be flattened and not rbd clones.
Additional info:
#cinder create --display-name vol5 1
# cinder create --source-volid 50351034-
Create three such cinder volumes from vol5.
Info on the third volume with rbd_max_clone_depth set to 2.
# rbd info volumes/
rbd image 'volume-
size 1024 MB in 256 objects
order 22 (4096 kB objects)
block_name_prefix: rbd_data.
format: 2
features: layering
flags:
parent: volumes/
overlap: 1024 MB
tags: | added: ceph drivers |
Changed in cinder: | |
importance: | Undecided → High |
Changed in cinder: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | liberty-3 → 7.0.0 |
Fix proposed to branch: master /review. openstack. org/205202
Review: https:/