Bug 1578329
| Summary: | Brick details stops showing data | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Filip Balák <fbalak> | ||||
| Component: | web-admin-tendrl-gluster-integration | Assignee: | gowtham <gshanmug> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Filip Balák <fbalak> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rhgs-3.4 | CC: | dahorak, gshanmug, nthomas, rhs-bugs, sankarshan, smukherj | ||||
| Target Milestone: | --- | ||||||
| Target Release: | RHGS 3.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| 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: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-09-04 07:06:18 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1503137 | ||||||
| Attachments: |
|
||||||
Created attachment 1436746 [details]
Volume Details page
This issue is fixed PR is under review https://github.com/Tendrl/gluster-integration/pull/645 https://github.com/Tendrl/gluster-integration/pull/644 I have wrongly moved this bug to modified, PR for this bug is merged in upstream so i am moving this bug to post. 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 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 |
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.