Description of problem: Clone getting created on Slave Node, on an already existing snapshot which is from Master to Slave Node Version-Release number of selected component (if applicable): 10.2.2-5.el7cp How reproducible: Always Steps to Reproduce: 1. Create an Image, take snap, protect it, create Clone 2. After the Clone and Parent Image sync's, try to create snap on an existing Image from Slave Node rbd clone test/liver3@snap3 test/bug --cluster slave Actual results: Clone gets created on Slave Node. Expected results: Slave Node should be read only and Clone creation should not be allowed. Additional info: Image Information from Slave Node: rbd image 'bug': size 11111 MB in 2778 objects order 22 (4096 kB objects) block_name_prefix: rbd_data.3aeb3d1b58ba format: 2 features: layering, exclusive-lock, object-map, fast-diff, deep-flatten parent: test/liver3@snap3 overlap: 11111 MB
Technically the parent is still read-only -- but we should probably disallow this case.
Upstream pull request: https://github.com/ceph/ceph/pull/10123
Verified with build - 10.2.3-8.el7cp.x86_64 Unable to create Clone on slave/remote cluster [root@magna078 ubuntu]# rbd clone pool1/bug2@snap2 pool1/slave2 --cluster slave 2016-10-22 21:01:40.175192 7f9a75f32d80 -1 librbd: parent is non-primary mirrored image rbd: clone error: (22) Invalid argument Hence moving to verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2815.html