Bug 1517080

Description of problem:
After performing replace-brick,the removed brick is still being reflected in web admin dashboard

Version-Release number of selected component (if applicable):
# rpm -qa|egrep "tendrl|gluster|kernel"
libvirt-daemon-driver-storage-gluster-3.2.0-14.el7_4.3.x86_64
samba-vfs-glusterfs-4.6.3-6.el7rhgs.x86_64
glusterfs-fuse-3.8.4-52.el7rhgs.x86_64
python-gluster-3.8.4-52.el7rhgs.noarch
gluster-nagios-common-0.2.4-1.el7rhgs.noarch
kernel-tools-libs-3.10.0-693.5.2.el7.x86_64
glusterfs-libs-3.8.4-52.el7rhgs.x86_64
tendrl-node-agent-1.5.4-5.el7rhgs.noarch
vdsm-gluster-4.17.33-1.2.el7rhgs.noarch
gluster-nagios-addons-0.2.9-1.el7rhgs.x86_64
nfs-ganesha-gluster-2.4.4-17.el7rhgs.x86_64
glusterfs-debuginfo-3.8.4-51.el7rhgs.x86_64
glusterfs-3.8.4-52.el7rhgs.x86_64
glusterfs-cli-3.8.4-52.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-52.el7rhgs.x86_64
tendrl-selinux-1.5.3-2.el7rhgs.noarch
tendrl-commons-1.5.4-4.el7rhgs.noarch
glusterfs-events-3.8.4-52.el7rhgs.x86_64
tendrl-gluster-integration-1.5.4-4.el7rhgs.noarch
kernel-tools-3.10.0-693.5.2.el7.x86_64
kernel-3.10.0-693.5.2.el7.x86_64
glusterfs-client-xlators-3.8.4-52.el7rhgs.x86_64
glusterfs-server-3.8.4-52.el7rhgs.x86_64
glusterfs-rdma-3.8.4-52.el7rhgs.x86_64
tendrl-collectd-selinux-1.5.3-2.el7rhgs.noarch
abrt-addon-kerneloops-2.1.11-48.el7.x86_64
kernel-3.10.0-693.2.2.el7.x86_64
glusterfs-geo-replication-3.8.4-52.el7rhgs.x86_64
kernel-3.10.0-693.2.1.el7.x86_64
glusterfs-api-3.8.4-52.el7rhgs.x86_64


How reproducible:


Steps to Reproduce:
1.Create 2 volumes 4*3 Distributed-Replicate volume
2.Perform replace brick operation (replace 1 brick) on one volume 
# gluster v replace-brick ganeshavol1 dhcp42-127.lab.eng.blr.redhat.com:/gluster/brick3/1 dhcp42-127.lab.eng.blr.redhat.com:/gluster/brick6/1test commit force
3.Check web admin dashboard 

Actual results:
web admin dashboard reflects the new brick along with removed brick.Status is not updated on web admin dashboard


Expected results:
Web admin dashboard should not show the removed brick in brick status


Additional info:

On dashboard it reflects 13 bricks.But actual bricks for the volume is 12


# gluster v info ganeshavol1
 
Volume Name: ganeshavol1
Type: Distributed-Replicate
Volume ID: 55c300dd-fecf-48ba-a57f-e472418f9b6e
Status: Started
Snapshot Count: 0
Number of Bricks: 4 x 3 = 12
Transport-type: tcp
Bricks:
Brick1: dhcp42-125.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick2: dhcp42-127.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick3: dhcp42-129.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick4: dhcp42-119.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick5: dhcp42-125.lab.eng.blr.redhat.com:/gluster/brick2/1
Brick6: dhcp42-127.lab.eng.blr.redhat.com:/gluster/brick2/1
Brick7: dhcp42-129.lab.eng.blr.redhat.com:/gluster/brick2/1
Brick8: dhcp42-119.lab.eng.blr.redhat.com:/gluster/brick2/1
Brick9: dhcp42-125.lab.eng.blr.redhat.com:/gluster/brick3/1
Brick10: dhcp42-127.lab.eng.blr.redhat.com:/gluster/brick6/1test
Brick11: dhcp42-129.lab.eng.blr.redhat.com:/gluster/brick3/1
Brick12: dhcp42-119.lab.eng.blr.redhat.com:/gluster/brick3/1
Options Reconfigured:
diagnostics.count-fop-hits: on
diagnostics.latency-measurement: on
transport.address-family: inet
nfs.disable: on
nfs-ganesha: disable
cluster.enable-shared-storage: disable