Bug 1578329 - Brick details stops showing data
Summary: Brick details stops showing data
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-gluster-integration
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.4.0
Assignee: gowtham
QA Contact: Filip Balák
URL:
Whiteboard:
Depends On:
Blocks: 1503137
TreeView+ depends on / blocked
 
Reported: 2018-05-15 09:48 UTC by Filip Balák
Modified: 2018-09-04 07:07 UTC (History)
6 users (show)

Fixed In Version: tendrl-ui-1.6.3-3.el7rhgs tendrl-gluster-integration-1.6.3-4.el7rhgs tendrl-monitoring-integration-1.6.3-4.el7rhgs tendrl-commons-1.6.3-6.el7rhgs tendrl-node-agent-1.6.3-6.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 07:06:18 UTC
Embargoed:


Attachments (Terms of Use)
Volume Details page (36.71 KB, image/png)
2018-05-15 09:49 UTC, Filip Balák
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github Tendrl gluster-integration issues 642 0 None None None 2018-05-17 08:33:35 UTC
Red Hat Product Errata RHSA-2018:2616 0 None None None 2018-09-04 07:07:07 UTC

Description Filip Balák 2018-05-15 09:48:26 UTC
Created attachment 1436745 [details]
logs and configuration files

Description of problem:
When Bricks Details page is open for a few minutes there usually is received response:
{"errors":{"message":"Invalid JSON received."}}
from `[hostname]/api/1.0/clusters/[cluster-id]/volumes/[volume-id]/bricks` API call. After this response is received the page stops to call this API call and user is shown blank page with no bricks.
This is shown in /var/log/tendrl/error.log.

Version-Release number of selected component (if applicable):
tendrl-ansible-1.6.3-3.el7rhgs.noarch
tendrl-api-1.6.3-3.el7rhgs.noarch
tendrl-api-httpd-1.6.3-3.el7rhgs.noarch
tendrl-commons-1.6.3-4.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-2.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-gluster-integration-1.6.3-2.el7rhgs.noarch
tendrl-monitoring-integration-1.6.3-2.el7rhgs.noarch
tendrl-node-agent-1.6.3-4.el7rhgs.noarch
tendrl-notifier-1.6.3-2.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.6.3-1.el7rhgs.noarch
glusterfs-3.12.2-9.el7rhgs.x86_64

How reproducible:
40%

Steps to Reproduce:
1. Import cluster with volume to WA.
2. Open Volumes page.
3. Click on the listed volume.
4. Brick page for selected volume is shown. Open console for the web (firebug).
5. Wait for few minutes.

Actual results:
There is repeatedly called `[hostname]/api/1.0/clusters/[cluster-id]/volumes/[volume-id]/bricks`. After a while one of the API calls return {"errors":{"message":"Invalid JSON received."}} and UI page goes blank.

Expected results:
There should be no random `Invalid JSON received.` messages.

Additional info:
In attached configuration and log files is described cluster that was freshly imported but it seems that the issue occurs more often when there is activity on the volume like inserting data.

Comment 1 Filip Balák 2018-05-15 09:49:28 UTC
Created attachment 1436746 [details]
Volume Details page

Comment 5 gowtham 2018-05-24 05:55:11 UTC
I have wrongly moved this bug to modified, PR for this bug is merged in upstream so i am moving this bug to post.

Comment 9 Filip Balák 2018-06-05 10:58:47 UTC
Seems to be fixed. BZ 1585715 was filled during testing.

Tested with:
tendrl-ansible-1.6.3-4.el7rhgs.noarch
tendrl-api-1.6.3-3.el7rhgs.noarch
tendrl-api-httpd-1.6.3-3.el7rhgs.noarch
tendrl-commons-1.6.3-6.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-4.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.6.3-4.el7rhgs.noarch
tendrl-node-agent-1.6.3-6.el7rhgs.noarch
tendrl-notifier-1.6.3-3.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.6.3-3.el7rhgs.noarch

Comment 11 errata-xmlrpc 2018-09-04 07:06:18 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:2616


Note You need to log in before you can comment on or make changes to this bug.