Bug 1344134

Summary: RGW Sync agent doesn't resync some objects after failover
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Michael J. Kidd <linuxkidd>
Component: RGWAssignee: Casey Bodley <cbodley>
Status: CLOSED ERRATA QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: urgent Docs Contact: Bara Ancincova <bancinco>
Priority: unspecified    
Version: 1.3.2CC: cbodley, ceph-eng-bugs, flucifre, gmeno, hnallurv, icolle, kbader, kdreyer, mbenjamin, mwatts, nlevine, owasserm, sweil, tserlin, vakulkar, vumrao
Target Milestone: rc   
Target Release: 1.3.3   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-0.94.7-5.el7cp, radosgw-agent-1.2.7-1.el7cp Ubuntu: ceph_0.94.7-3redhat1trusty, radosgw-agent_1.2.7-2redhat Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
.The "radosgw-agent fully sync" mode now copies only changed objects With this update, the `radosgw-agent` in `full sync` mode copies only objects that have changed, instead of all of them, when synchronizing objects between two Ceph Object Gateways after a failover.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-29 12:59:44 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:
Bug Depends On:    
Bug Blocks: 1348597, 1372735    

Comment 4 Michael J. Kidd 2016-06-08 20:45:42 UTC 
Created attachment 1166108 [details]
RGW Logs from 'am' zone
Comment 13 Michael J. Kidd 2016-06-09 15:59:22 UTC 
Marcus:
 - Yehuda suggested continuing work on reproduction internally so we can test the new code to ensure it's will achieve the end goal.
Comment 17 Casey Bodley 2016-06-13 14:50:51 UTC 
Added upstream pull requests for the hammer backport (https://github.com/ceph/ceph/pull/9671) and sync agent (https://github.com/ceph/radosgw-agent/pull/44).
Comment 56 errata-xmlrpc 2016-09-29 12:59:44 UTC 
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-1972.html