Bug 1641413

Summary:	Volume utilization calculation not happening for all volumes when any one volume bricks are down
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	gowtham <gshanmug>
Component:	web-admin-tendrl-gluster-integration	Assignee:	umanga <uchapaga>
Status:	CLOSED ERRATA	QA Contact:	Filip Balák <fbalak>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	fbalak, mbukatov, nthomas, rhs-bugs, sankarshan
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.4.z Batch Update 2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tendrl-gluster-integration-1.6.3-13.el7rhgs	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-12-17 17:06:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description gowtham 2018-10-22 03:29:31 UTC

Description of problem:

I had created gluster cluster with 3 volumes and I manually brought down all bricks in one of the volumes. After import volume utilization calculation does not happen for all volumes. 

Version-Release number of selected component (if applicable):


How reproducible:
100% reprodusable

Steps to Reproduce:
1. Create gluster cluster with at least two volumes(volume of any time)
2. Bring down all bricks in any one volume
3. Import the gluster cluster using WA
4. Check volume utilization dashbaord in grafana


Actual results:

bricks down in one volume is affecting all volumes volume utilization calculation

Expected results:

one volume bricks down should not affect other volumes volume utilization calculation.

Additional info:

we are not considering volume which has status down for volume utilization but in this case, all bricks are down but volume status is still up, so we are considering that volume also for utilization calculation, So the logic goes wrong.

Comment 2 gowtham 2018-10-23 05:44:06 UTC

A version of gluster-integration to reproduce the problem is:  
    tendrl-gluster-integration-1.6.3-12.el7rhgs

Comment 5 Filip Balák 2018-11-09 12:18:55 UTC

I have tested this on cluster with 3 volumes and I was able to reproduce it with version:
tendrl-monitoring-integration-1.6.3-14.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-api-1.6.3-7.el7rhgs.noarch
tendrl-api-httpd-1.6.3-7.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-14.el7rhgs.noarch
tendrl-ansible-1.6.3-8.el7rhgs.noarch
tendrl-commons-1.6.3-13.el7rhgs.noarch
tendrl-node-agent-1.6.3-10.el7rhgs.noarch
tendrl-ui-1.6.3-11.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-notifier-1.6.3-4.el7rhgs.noarch

I tested this 3x times with:
tendrl-monitoring-integration-1.6.3-15.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-api-1.6.3-8.el7rhgs.noarch
tendrl-api-httpd-1.6.3-8.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-15.el7rhgs.noarch
tendrl-ansible-1.6.3-9.el7rhgs.noarch
tendrl-commons-1.6.3-13.el7rhgs.noarch
tendrl-node-agent-1.6.3-11.el7rhgs.noarch
tendrl-ui-1.6.3-12.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-notifier-1.6.3-4.el7rhgs.noarch

And it seems ok. All panels in Capacity row of Volume dashboard for not affected volumes are showing correct values (panels Weekly Growth Rate and Weeks Remaining were tested only once). --> VERIFIED

Comment 6 errata-xmlrpc 2018-12-17 17:06:56 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:3829