Bug 1472874

Summary: Stale bucket index entries are left over after object deletions due to invalid timespan issues
Product: Red Hat Ceph Storage Reporter: Benjamin Schmaus <bschmaus>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: vidushi <vimishra>
Severity: high Docs Contact: Erin Donnelly <edonnell>
Priority: medium    
Version: 2.3CC: anharris, bschmaus, cbodley, ceph-eng-bugs, edonnell, hnallurv, kbader, kdreyer, mbenjamin, mhackett, owasserm, sweil
Target Milestone: rc   
Target Release: 3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-12.1.2-1.el7cp Ubuntu: ceph_12.1.2-2redhat1xenial Doc Type: Bug Fix
Doc Text:
.Deleting objects no longer leaves stale bucket index entries Previously, when objects were removed from the Ceph Object Gateway, the `radosgw` daemon could fail to remove the entries of the deleted objects due to a time scaling error. This bug has been fixed, and `radosgw` removes the bucket index entries as expected.
Story Points: ---
Clone Of:
: 1479771 (view as bug list) Environment:
Last Closed: 2017-12-05 23:36:49 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:
Bug Depends On:    
Bug Blocks: 1473188, 1479771, 1494421    

Description Benjamin Schmaus 2017-07-19 15:02:12 UTC
Description of problem:

Stale bucket index entries are left over after object deletions due to invalid timespan issues

https://github.com/ceph/ceph/pull/16289/files


Version-Release number of selected component (if applicable):
2.3

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 16 errata-xmlrpc 2017-12-05 23:36:49 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://access.redhat.com/errata/RHBA-2017:3387