Bug 1446120

Summary: [RBD-mirror] - Disabling image feature in primary cluster is not getting reflected in secondary cluster
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: RBDAssignee: Jason Dillaman <jdillama>
Status: CLOSED DUPLICATE QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.3CC: ceph-eng-bugs
Target Milestone: rc   
Target Release: 2.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-27 11:47:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
A sample doc of terminal log having information on steps I followed and corresponding terminal output none

Description Vasishta 2017-04-27 09:54:08 UTC 
Description of problem:
Disabling some image features of an image in 'pool mirroring' enabled pool in primary cluster is not getting reflected in corresponding image of corresponding pool in secondary cluster.

Version-Release number of selected component (if applicable):
ceph version 10.2.7-13.el7cp 

How reproducible:
Always

Steps to Reproduce:
1. Follow section 4.5 in Block Device guide to Configure pool mirroring.
2. Create a image and enable journaling feature and make sure that it has got mirrored to secondary cluster.
3. For above image in primary cluster disable image features like fast-diff, object-map and deep-flatten 

Actual results:
Image in secondary doesn't reflect corresponding image in primary cluster properly

Expected results:
Image in secondary must reflect corresponding image in primary cluster properly

Additional info:
Couldn't observe any issue with data synchronization.
Comment 2 Vasishta 2017-04-27 09:56:39 UTC 
Created attachment 1274555 [details]
A sample doc of terminal log having information on steps I followed and corresponding terminal output
Comment 3 Jason Dillaman 2017-04-27 11:47:12 UTC 

*** This bug has been marked as a duplicate of bug 1344262 ***