Bug 1116168

Summary:	RFE: Allow geo-replication to slave Volume in same trusted storage pool
Product:	[Community] GlusterFS	Reporter:	Andrew Hatfield <ahatfiel>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	avishwan, bugs, smohan, vbellur
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-19 05:20:08 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 Andrew Hatfield 2014-07-03 23:41:56 UTC

Description of problem:

With the new geo-replication we are now unable to configure geo-replication between a Master and Slave Volume on the same Trusted Storage Pool.

There is a valid use-case to allow users to asynchronously geo-replicate Volumes within the same Trusted Storage Pool.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Niels de Vos 2014-11-27 14:45:20 UTC

Feature requests make most sense against the 'mainline' release, there is no ETA for an implementation and requests might get forgotten when filed against a particular version.

Comment 2 Vijay Bellur 2018-11-19 05:50:01 UTC

Migrated to github:

https://github.com/gluster/glusterfs/issues/556

Please follow the github issue for further updates on this bug.