[Bugs] [Bug 966207] replace-brick commit force refuses to work when it cannot resolve source brick

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=966207

Earl Ruby <eruby at knowledgematters.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eruby at knowledgematters.net



--- Comment #1 from Earl Ruby <eruby at knowledgematters.net> ---
Still happening on GlusterFS 3.7. I created a 3 node cluster (gfs1, gfs2,
gfs3), 3 bricks each, then killed gfs2. I added a 4th host (gfs4) and used
"peer probe" to add it to the cluster. I can't detach gfs2 because it has
bricks in the cluster, and I can't replace gfs2 bricks with gfs4 bricks because
it claims that the gfs2 bricks don't exist. Check it out:

root at gfs1:~# gluster volume info
Volume Name: volume1
Type: Distributed-Replicate
Volume ID: 168a6859-91a5-451e-9c32-ab531b79df16
Status: Started
Number of Bricks: 3 x 3 = 9
Transport-type: tcp
Bricks:
Brick1: gfs1:/data/brick1/files
Brick2: gfs2:/data/brick1/files
Brick3: gfs3:/data/brick1/files
Brick4: gfs1:/data/brick2/files
Brick5: gfs2:/data/brick2/files
Brick6: gfs3:/data/brick2/files
Brick7: gfs1:/data/brick3/files
Brick8: gfs2:/data/brick3/files
Brick9: gfs3:/data/brick3/files
Options Reconfigured:
nfs.disable: off
features.quota-deem-statfs: on
features.inode-quota: on
features.quota: on
performance.readdir-ahead: on

root at gfs1:~# gluster volume replace-brick volume1 gfs2:/data/brick1/files
gfs4:/data/brick1/files commit force
volume replace-brick: failed: brick: gfs2:/data/brick1/files does not exist in
volume: volume1

I worked around the problem by adding gfs2 to /etc/hosts on gfs1, gfs3, and
gfs4. Once I did that I could replace the bricks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.