Created attachment 1457792 [details] Graphite utilization data from node with removed bricks Description of problem: WA keeps collecting volume data related to node/bricks even after all bricks from the node are removed. Version-Release number of selected component (if applicable): tendrl-ansible-1.6.3-5.el7rhgs.noarch tendrl-api-1.6.3-4.el7rhgs.noarch tendrl-api-httpd-1.6.3-4.el7rhgs.noarch tendrl-commons-1.6.3-8.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-6.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-6.el7rhgs.noarch tendrl-node-agent-1.6.3-8.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-6.el7rhgs.noarch How reproducible: 100% Steps to Reproduce: 1. Import gluster cluster with created volume into WA. 2. Remove bricks on several nodes: gluster volume remove-brick <volname> <hostname>:<brickpath> ... <hostname>:<brickpath> start gluster volume remove-brick <volname> <hostname>:<brickpath> ... <hostname>:<brickpath> commit 3. Wait 5 minutes. 4. Check http://<hostname>:10080/render/?target=tendrl.clusters.<cluster>.volumes.<volname>.nodes.<nodewithdeletedbricks>.rebalance_skipped&format=json&from=-5min or some other relevant graphite target. Actual results: There are returned some empty records that WA tried to collect. Expected results: There should be no records returned. Additional info:
With current version I see that the data is not collected and reproducer returns null values. Tested with: tendrl-ansible-1.6.3-5.el7rhgs.noarch tendrl-api-1.6.3-4.el7rhgs.noarch tendrl-api-httpd-1.6.3-4.el7rhgs.noarch tendrl-commons-1.6.3-9.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-7.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-7.el7rhgs.noarch tendrl-node-agent-1.6.3-9.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-8.el7rhgs.noarch
@Gowtham, is this expected behavior? If so what is the action required here?
As per current implementation when the brick is removed then we are actually removing brick related information under node and volumes, so it is already resolved, Please test this scenario with the latest build.
I have verified with the latest build and its fixed already.