Description of problem: ======================= Have multiple secondary sites. Image syncing on 2nd secondary fails if syncing finished on 1st secondary first. Version-Release number of selected component (if applicable): ============================================================= 10.2.5-13.el7cp.x86_64 How reproducible: ================= always Steps to Reproduce: ================== 1. have 3 cluster. Site A-'master' being primary and Site B-'slave1' and site C-'slave2' are secondary sites (site B has bidirectional relation with A while C has one-directional) 2. enable pool level mirroring 3. create Image but do not enable journaling. 4. Do some I/O using bench-write 5. enable journaling and keep doing I/O on image 6. when sync reaches 20+% stop rbd-mirror on 'master' cluster(Site A) 7. keep checking image status on Site B and Site c. 8. after few seconds start daemon on Site A. 9. stop I/O on image Actual results: =============== Syncing on Site B is successful but on Site C it failed after sometime [root@magna099 ubuntu]# rbd mirror image status con/re1 --cluster slave2 re1: global_id: 1d65a791-cc3e-4fb2-a02e-aec830f0113c state: up+syncing description: bootstrapping, IMAGE_COPY/COPY_OBJECT 37% last_update: 2017-02-19 19:03:37 [root@magna099 ubuntu]# rbd mirror image status con/re1 --cluster slave2 re1: global_id: 1d65a791-cc3e-4fb2-a02e-aec830f0113c state: up+syncing description: bootstrapping, IMAGE_COPY/COPY_OBJECT 50% last_update: 2017-02-19 19:03:57 [root@magna099 ubuntu]# rbd mirror image status con/re1 --cluster slave2 re1: global_id: 1d65a791-cc3e-4fb2-a02e-aec830f0113c state: up+error description: error bootstrapping replay last_update: 2017-02-19 19:04:19 Expected results: ================= Image should sync to all secondary sites Additional info:
Multiple secondaries are not a blocker for release 2.2.
I believe you should also be able to hit this condition if you delete an old snapshot from the primary image while the non-primary cluster is performing a full image-sync.
timeframe for a fix?
verified with build - 10.2.5-34.el7cp.x86_64 working as expected 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/RHBA-2017-0514.html