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 1340482

Summary:	[rbd-mirror] image deletions are not propagated to peer cluster
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Jason Dillaman <jdillama>
Component:	RBD	Assignee:	Jason Dillaman <jdillama>
Status:	CLOSED ERRATA	QA Contact:	Hemanth Kumar <hyelloji>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	amaredia, ceph-eng-bugs, hnallurv, hyelloji
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:49 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 14:03:40 UTC

Description of problem:
When a primary image is deleted, this deletion operation should be propagated to the non-primary cluster.  Additionally, if replication is disabled for the primary image, the non-primary image should be deleted.

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

How reproducible:
100%

Steps to Reproduce:
1. Delete a primary image or disabling mirroring on the primary image

Actual results:
The image remains in the non-primary cluster.  If a new image with the same name is recreated or if replication is re-enabled, you will receive a split-brain error.

Expected results:
The non-primary image will be deleted.

Additional info:

Comment 4 Hemanth Kumar 2016-06-27 12:45:50 UTC

Deletion of image and disabling the image is propagated to the remote rbd host.
Verified in v10.2.2-5 build.
Moving to verified state

Comment 6 errata-xmlrpc 2016-08-23 19:39:49 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