summaryrefslogtreecommitdiffstats
path: root/cli/src/cli-cmd-volume.c
diff options
context:
space:
mode:
authorKotresh HR <khiremat@redhat.com>2018-11-20 12:36:55 +0530
committerKotresh HR <khiremat@redhat.com>2018-11-28 05:04:10 +0000
commit4c3cfd0f85c1044c804b2c31d99a4bc3b1c1fe49 (patch)
tree6082d290b71f6091109814460cac3b244f42924d /cli/src/cli-cmd-volume.c
parentd6383f22f0b6d66c9596c05da7fcf27599615b01 (diff)
geo-rep: Fix permissions with non-root setup
Problem: In non-root fail-over/fail-back(FO/FB), when slave is promoted as master, the session goes to 'Faulty' Cause: The command 'gluster-mountbroker <mountbroker-root> <group>' is run as a pre-requisite on slave in non-root setup. It modifies the permission and group of following required directories and files recursively [1] /var/lib/glusterd/geo-replication [2] /var/log/glusterfs/geo-replication-slaves In a normal setup, this is executed on slave node and hence doing it recursively is not an issue on [1]. But when original master becomes slave in non-root during FO/FB, it contains ssh public keys and modifying permissions on them causes geo-rep to fail with incorrect permissions. Fix: Don't do permission change recursively. Fix permissions for required files. Backport of: > Patch: https://review.gluster.org/#/c/glusterfs/+/21689/ > fixes: bz#1651498 > Change-Id: I68a744644842e3b00abc26c95c06f123aa78361d > Signed-off-by: Kotresh HR <khiremat@redhat.com> (cherry picked from commit b2776b1ec1ad845ba568c4439bca3b57cc4d2592) fixes: bz#1654118 Change-Id: I68a744644842e3b00abc26c95c06f123aa78361d Signed-off-by: Kotresh HR <khiremat@redhat.com>
Diffstat (limited to 'cli/src/cli-cmd-volume.c')
0 files changed, 0 insertions, 0 deletions