Bug 1125818

Summary:	geo-rep: changelog_register fails when geo-rep started after session creation.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED ERRATA	QA Contact:	Bhaskar Bandari <bbandari>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	aavati, ajha, avishwan, bbandari, csaba, david.macdonald, nlevinki, nsathyan, ssamanta
Target Milestone:	---
Target Release:	RHGS 3.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.6.0.27-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1125843 (view as bug list)		Environment:
Last Closed:	2014-09-22 19:45:12 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:
Bug Depends On:
Bug Blocks:	1125843

Description Kotresh HR 2014-08-01 06:52:41 UTC

Description of problem:
changelog_register fails with ENOENT when geo-rep started just after session creation. It goes to Hybrid Crawl and never goes to changelog mode untill a stop and start of geo-rep.

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


How reproducible:
Happens everytime.

Steps to Reproduce:
1. Create geo-rep session between master and slave
2. Start the geo-rep between master and slave
3. Check the log to see changelog_register failure or status to see "Hybrid Crawl"

Actual results:
changelog_register fails and always be in xsync mode

Expected results:
changelog_register should not fail, it should got to history, xsync and then changelog.

Additional info:

Comment 2 Kotresh HR 2014-08-04 07:44:26 UTC

Upstream Patch:
http://review.gluster.org/8399
Downstream Patch:
https://code.engineering.redhat.com/gerrit/#/c/30246/

Comment 3 Vijaykumar Koppad 2014-08-05 06:30:39 UTC

verified on the build glusterfs-3.6.0.27-1

Comment 6 errata-xmlrpc 2014-09-22 19:45:12 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.

http://rhn.redhat.com/errata/RHEA-2014-1278.html