Bug 1340476

Summary:	[rbd-mirror] multiple replicated pools results in incorrect replication status
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Jason Dillaman <jdillama>
Component:	RBD	Assignee:	Jason Dillaman <jdillama>
Status:	CLOSED ERRATA	QA Contact:	Tanay Ganguly <tganguly>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	amaredia, ceph-eng-bugs, hnallurv, hyelloji, kurs
Target Milestone:	rc
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-10.2.1-12.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 19:39:45 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 2016-05-27 13:45:00 UTC

Description of problem:
When a cluster has two or more replicated pools, the rbd-mirror daemon will attempt to replicate a single image multiple times (once for each pool).  This results in the status ping-ponging back-and-forth between replaying and bootstrapping.  It also results in numerous error messages in the logs.

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


How reproducible:
100%

Steps to Reproduce:
1. create two or more replicated pools
2. put at least one replicated image in a pool

Actual results:
Use 'rbd mirror pool status' to see the health warning

Expected results:
No health warning.

Additional info:

Comment 6 Hemanth Kumar 2016-06-16 18:27:40 UTC

Not seeing any errors while replicating 2 0r more pools 
Verified by checking the pool status,
# rbd mirror pool status pool3 --cluster master
health: OK
images: 196 total
    196 stopped

Moving to verified state.

Comment 8 errata-xmlrpc 2016-08-23 19:39:45 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-2016-1755.html