Bug 2270785

Summary:	[CephFS - Consistency Group] - QuiesceDB may roll back when a rank membership is unstable
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Leonid Usov <lusov>
Component:	CephFS	Assignee:	Leonid Usov <lusov>
Status:	CLOSED ERRATA	QA Contact:	sumr
Severity:	high	Docs Contact:	Akash Raj <akraj>
Priority:	high
Version:	7.1	CC:	akraj, ceph-eng-bugs, cephqe-warriors, hyelloji, pdonnell, tserlin, vereddy
Target Milestone:	---
Target Release:	7.1
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	ceph-18.2.1-79.el9cp	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-13 14:30:11 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:	2267614, 2298578, 2298579

Description Leonid Usov 2024-03-21 18:05:18 UTC

Description of problem:


Changes to the manager threading model have created a race condition when a rank joins the cluster again before it has had a chance to process a prior loss of membership. In such a case, membership updates coalesce, and the rank may wrongly assume that its stale quiesce database from the past membership is still valid.

Comment 10 errata-xmlrpc 2024-06-13 14:30:11 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 (Critical: Red Hat Ceph Storage 7.1 security, enhancements, 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-2024:3925