Bug 1514007

Summary: Objects left after calling radosgw-admin bucket rm --purge-objects
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Orit Wasserman <owasserm>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED CURRENTRELEASE QA Contact: Tejas <tchandra>
Severity: low Docs Contact: Erin Donnelly <edonnell>
Priority: low    
Version: 3.0CC: anharris, cbodley, ceph-eng-bugs, edonnell, jbautist, kbader, mbenjamin, sweil
Target Milestone: rc   
Target Release: 3.*   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
.Object leaking can occur after using `radosgw-admin bucket rm --purge-objects` In the Ceph Object Gateway, the `radosgw-admin bucket rm --purge-objects` command is supposed to remove all object from a bucket. However, in some cases, some of the objects are left in the bucket. This is caused by the `RGWRados::gc_aio_operate()` operation abandoning on shutdown. To work around this problem, remove the objects by using the `rados rm` command.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-22 05:23:03 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: 1494421    

Description Orit Wasserman 2017-11-16 13:32:14 UTC 
Description of problem:
There could be object leaking after calling radosgw-admin bucket rm  --purge-objects.
this due to RGWRados::gc_aio_operate() ops abandoned on shutdown.

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


How reproducible:
Create a large bucket

Steps to Reproduce:
1. remove the bucket
2.
3.

Actual results:
some of the objects are left

Expected results:
No objects left

Additional info:
Comment 9 Giridhar Ramaraju 2019-08-05 13:10:27 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 10 Giridhar Ramaraju 2019-08-05 13:11:31 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 11 Tejas 2019-08-22 05:20:57 UTC 
*** Bug 1504912 has been marked as a duplicate of this bug. ***