Bug 1685734

Summary:	MDS `cache drop` command does not timeout as expected
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Patrick Donnelly <pdonnell>
Component:	CephFS	Assignee:	Patrick Donnelly <pdonnell>
Status:	CLOSED ERRATA	QA Contact:	subhash <vpoliset>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.1	CC:	ceph-eng-bugs, edonnell, sweil, tchandra, tserlin
Target Milestone:	rc
Target Release:	3.3
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.12-22.el7cp Ubuntu: ceph_12.2.12-18redhat1	Doc Type:	Bug Fix
Doc Text:	.The `drop cache` command completes as expected Previously, when executing the administrative `drop cache` command, the Metadata Server (MDS) did not detect that the clients could not return more capabilities, and the command would not complete. With this update, the MDS now detects the clients cannot return any more capabilities, and the command completes.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-21 15:10: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:
Embargoed:
Bug Depends On:
Bug Blocks:	1726135

Description Patrick Donnelly 2019-03-05 22:49:51 UTC

Description of problem:

See: http://tracker.ceph.com/issues/38348

This is tested in upstream QA.

Comment 6 Giridhar Ramaraju 2019-08-05 13:06:47 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 7 Giridhar Ramaraju 2019-08-05 13:09:24 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 9 errata-xmlrpc 2019-08-21 15:10: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/RHSA-2019:2538