fbfcb0ad2a
A commonly faced problem among glusterfs users is: after a fresh installation of glusterfs in a virtual machine, the VM image is cloned to make multiple instances of the server. This breaks glusterd because right after glusterfs installation on the first boot glusterd would have created the node UUID and this gets inherited into the clone. The result is wierd behavior at the time of peer probe where glusterd does not (yet) deal with UUID collisions in a user friendly way. To handle it gluster peer reset command is implemented which upon execution changes the uuid of local glusterd. Change-Id: If207dd2ad93ab94ef1a3253f409c21c442975f87 BUG: 811493 Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com> Reviewed-on: http://review.gluster.org/3637 Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@redhat.com>
19 lines
324 B
Bash
Executable File
19 lines
324 B
Bash
Executable File
#!/bin/bash
|
|
|
|
. $(dirname $0)/../include.rc
|
|
|
|
cleanup;
|
|
|
|
TEST glusterd
|
|
TEST pidof glusterd
|
|
TEST $CLI system uuid reset;
|
|
|
|
uuid1=$(grep UUID /var/lib/glusterd/glusterd.info | cut -f 2 -d "=");
|
|
|
|
TEST $CLI system uuid reset;
|
|
uuid2=$(grep UUID /var/lib/glusterd/glusterd.info | cut -f 2 -d "=");
|
|
|
|
TEST [ $uuid1 != $uuid2 ]
|
|
|
|
cleanup
|