Bug 1612378

Summary:	CephVolumeClient: volume isolation via data pools has race condition
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Patrick Donnelly <pdonnell>
Component:	CephFS	Assignee:	Patrick Donnelly <pdonnell>
Status:	CLOSED ERRATA	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.0	CC:	anharris, ceph-eng-bugs, ceph-qe-bugs, john.spray, rperiyas, rraja
Target Milestone:	z1
Target Release:	3.1
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.5-47.el7cp Ubuntu: ceph_12.2.5-32redhat1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-09 00:59:21 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:

Description Patrick Donnelly 2018-08-03 21:11:51 UTC

Description of problem:

The addition of a data pool to the MDSMap races with the setting of the volume (directory) to that data pool. The MDS will refuse the setting if it does not receive the new MDSMap in time.

See also: http://tracker.ceph.com/issues/25141

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

3.0

How reproducible:

Very rare. Found in upstream testing.

Comment 4 Ramakrishnan Periyasamy 2018-08-09 04:23:48 UTC

Hi Patrick,

Do we have steps to verify this bug ? if not regression and sanity testing is enough ?

--Ramakrishnan

Comment 6 Patrick Donnelly 2018-08-09 21:59:04 UTC

(In reply to Ramakrishnan Periyasamy from comment #4)
> Hi Patrick,
> 
> Do we have steps to verify this bug ? if not regression and sanity testing
> is enough ?
> 
> --Ramakrishnan

Running upstream QA should be sufficient.

Comment 14 errata-xmlrpc 2018-11-09 00:59:21 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-2018:3530