Bug 2224243

Summary: mds: cap revoke and cap update's seqs mismatched
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Xiubo Li <xiubli>
Component: CephFSAssignee: Xiubo Li <xiubli>
Status: CLOSED ERRATA QA Contact: Hemanth Kumar <hyelloji>
Severity: medium Docs Contact: Akash Raj <akraj>
Priority: unspecified    
Version: 5.3CC: akraj, bmcmurra, ceph-eng-bugs, cephqe-warriors, hyelloji, tserlin, vshankar
Target Milestone: ---   
Target Release: 6.1z2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-17.2.6-127.el9cp Doc Type: Bug Fix
Doc Text:
.Revocation requests no longer get stuck Previously, before the revoke request was sent out, which would increase the 'seq', if the clients released the corresponding caps and sent out the cap update request with the old `seq`, the MDS would miss checking the `seq`(s) and cap calculation. Due to this, the revocation requests would be stuck infinitely and would throw warnings about the revocation requests not responding from clients. With this fix, an acknowledgement is always sent for revocation requests and they no longer get stuck.
 Story Points: ---
Clone Of: 2224242 Environment:
Last Closed: 2023-10-12 16:34:33 UTC Type: ---
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: 2235257    

Description Xiubo Li 2023-07-20 09:05:03 UTC 
+++ This bug was initially created as a clone of Bug #2224242 +++

If just before the revoke request, which will increase the 'seq', is
sent out the clients released the corresponding caps and sent out
the cap update request with old 'seq', the mds will miss checking
the seqs and calculating the caps.

We should always send an ack for revoke requests.

Fixes: https://tracker.ceph.com/issues/61782

--- Additional comment from RHEL Program Management on 2023-07-20 09:04:27 UTC ---

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.
Comment 1 RHEL Program Management 2023-07-20 09:05:18 UTC 
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.
Comment 8 errata-xmlrpc 2023-10-12 16:34:33 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 (Moderate: Red Hat Ceph Storage 6.1 security, enhancement, and bug fix update), 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-2023:5693
Comment 9 Manny 2024-07-17 14:25:26 UTC 
*** Bug 2250199 has been marked as a duplicate of this bug. ***