Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1744529

Summary:	fetching config overrides can result in crash due to unsafe observer calls
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Venky Shankar <vshankar>
Component:	RBD	Assignee:	Jason Dillaman <jdillama>
Status:	CLOSED ERRATA	QA Contact:	Madhavi Kasturi <mkasturi>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.3	CC:	ceph-eng-bugs, ceph-qe-bugs, jdillama, mmurthy, pdonnell, tchandra, tserlin
Target Milestone:	z2
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.12-80.el7cp Ubuntu: ceph_12.2.12-73redhat1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-19 17:59: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:

Description Venky Shankar 2019-08-22 10:49:52 UTC

[applies to all components, but keeping it as RBD as the tracker ticket was reported against that]

Description of problem:
Thread unsafe invocations of config observers (for fetching config overrides) results in crashes (as mentioned in the ceph tracker ticket -- python based tools using rbd python api kept crashing).

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

How reproducible:
easily reproducible


Steps to Reproduce:
ceph tracker ticket has reproducer scripts attached.

Actual results:
App crashes.

Expected results:
no crashes/backtraces, clean init/shutdown and execution of the app.

Comment 3 Jason Dillaman 2019-09-11 14:13:24 UTC

Bumping to z2 since it's a non-trivial cherry-pick is require for RHCS 3.x.

Comment 13 errata-xmlrpc 2019-12-19 17:59: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:4353