Bug 1715946

Summary: [RGW-NFS]: objects stored on nfs mount may have inconsistent tail tag and fail to gc
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Matt Benjamin (redhat) <mbenjamin>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: Tejas <tchandra>
Severity: medium Docs Contact:
Priority: low    
Version: 3.2CC: cbodley, ceph-eng-bugs, ceph-qe-bugs, edonnell, kbader, mbenjamin, sweil, tchandra, tserlin
Target Milestone: rc   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.12-15.el7cp Ubuntu: ceph_12.2.12-14redhat1 Doc Type: Bug Fix
Doc Text:
.Space is no longer leaked when deleting objects via NFS Previously, the Ceph Object Gateway NFS implementation incorrectly set a value used to construct a key subsequently used to set garbage collection (GC) on shadow objects. Deleting an object via NFS, as opposed to S3 or Swift, could cause space to be leaked. With this update, the GC tag is now set correctly and space is not leaked when deleting objects via NFS.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-21 15:11:09 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: 1726135    

Description Matt Benjamin (redhat) 2019-05-31 17:31:38 UTC 
Description of problem:
The logic for associating RGW request id tokens with tail objects was broken by NFS mapping of writes to multiple "continued requests."  This could cause objects with tail chunks to fail to gc after deletion.

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

Steps to Reproduce:
See upstream tracker.
Comment 13 errata-xmlrpc 2019-08-21 15:11:09 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/RHSA-2019:2538