Description of problem in RHS 3.0 Early Access release:
Run the config command on an active geo-replication session and it shows:
Steps to Reproduce:
1. Start geo-replication
2. Run the geo-replication master slave config
3. Look at the output
It should show the actual path.
I see where /nonexistent/gsyncd is set. It is basically part of some template file, right? Can we just change the template file and replace /nonexistent/gsyncd with the real path that way this never comes up? The problem here is that a customer is running in to this due to issues with running the create command for geo-replication. They have a weird security software layer that puts some things in non-standard locations.
Fix to be done in $SRC/geo-replication/syncdaemon/configinterface.py.in
Handle this config key as special case.
Geo-replication support added to Glusterd2 project, which will be available with Gluster upstream 4.0 and 4.1 releases.
Most of the issues already fixed with issue https://github.com/gluster/glusterd2/issues/271 and remaining fixes are noted in issue https://github.com/gluster/glusterd2/issues/557
We can close these issues since we are not planning any fixes for 3.x series.