Bug 1410921

Summary:	[rbd-mirror] sporadic image replayer shut down failure
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Jason Dillaman <jdillama>
Component:	RBD	Assignee:	Jason Dillaman <jdillama>
Status:	CLOSED ERRATA	QA Contact:	Rachana Patel <racpatel>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	ceph-eng-bugs, hnallurv
Target Milestone:	rc	Keywords:	CodeChange
Target Release:	2.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-10.2.5-7.el7cp Ubuntu: ceph_10.2.5-3redhat1xenial	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-14 15:47:55 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 Jason Dillaman 2017-01-06 20:57:25 UTC

Description of problem:
Possible live-lock of rbd-mirror daemon's image replayer state machine during stop

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

How reproducible:
rare -- integration test rbd_mirror_stress occasionally hits the issue

Steps to Reproduce:
1. mirror an image
2. stop rbd-mirror on the non-primary
3. inject lots of IO events into the primary image
4. restart rbd-mirror on the non-primary site
5. while rbd-mirror is replaying the IO events, attempt a graceful shut down

Actual results:
There is a possibility that the image replayer state machine will get live-locked in the STOPPING state.

Expected results:
The image replayer should cleanly shut down.

Additional info:

Comment 5 Rachana Patel 2017-02-23 03:13:16 UTC

verified with version - 10.2.5-29.el7cp.x86_64

followed steps mentioned in description and works for me hence moving to verified

Comment 7 errata-xmlrpc 2017-03-14 15:47:55 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://rhn.redhat.com/errata/RHBA-2017-0514.html