New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

luminous: rgw: setxattrs call leads to different mtimes for bucket index and object #17856

Merged
merged 1 commit into from Oct 27, 2017

Conversation

@smithfarm
Contributor

smithfarm commented Sep 21, 2017

rgw: rgw_rados: set_attrs now sets the same time for BI & object
`RGWRados::set_attrs()` used to set slightly different mtimes for the
object and in the bucket dir entry as we do an object write and set the
time at bucket index as the time at that point. Fix this by using the
setting the same mtime for the object as well.

Fixes: http://tracker.ceph.com/issues/21200
Signed-off-by: Abhishek Lekshmanan <abhishek@suse.com>
(cherry picked from commit 87e8e89)

@smithfarm smithfarm self-assigned this Sep 21, 2017

@smithfarm smithfarm added this to the luminous milestone Sep 21, 2017

@smithfarm smithfarm added bug fix core rgw and removed core labels Sep 21, 2017

@smithfarm smithfarm requested a review from yehudasa Sep 21, 2017

@theanalyst

This comment has been minimized.

Show comment
Hide comment
@theanalyst

theanalyst Oct 27, 2017

Member

Passed a teuthology run at http://tracker.ceph.com/issues/21830#note-8 and will be merged when approved

Member

theanalyst commented Oct 27, 2017

Passed a teuthology run at http://tracker.ceph.com/issues/21830#note-8 and will be merged when approved

@theanalyst theanalyst merged commit 3db3ca9 into ceph:luminous Oct 27, 2017

4 checks passed

Docs: build check OK - docs built
Details
Signed-off-by all commits in this PR are signed
Details
Unmodified Submodules submodules for project are unmodified
Details
make check make check succeeded
Details

@smithfarm smithfarm deleted the smithfarm:wip-21444-luminous branch Oct 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment