Description of problem: With this change https://review.gluster.org/#/c/glusterfs/+/21739/. we are making Slave volume read-only by default during geo-rep setup. But when separate ssh key is given for non root user setting slave volume read-only option results in failure. Version-Release number of selected component (if applicable): How reproducible: Always Additional info: Solution: Check for extra param in case separate key is given for non-root user and take action accordingly.
REVIEW: https://review.gluster.org/21874 (geo-rep : fix slave volume read-only option) posted (#1) for review on master by Sunny Kumar
REVIEW: https://review.gluster.org/21874 (geo-rep : fix slave volume read-only option) posted (#2) for review on master by Amar Tumballi
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/