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):
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"
changelog_register fails and always be in xsync mode
changelog_register should not fail, it should got to history, xsync and then changelog.
verified on the build glusterfs-126.96.36.199-1
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.