Red Hat Bugzilla – Bug 1564510
Grafana dashboards with new nodes are created before user initiates cluster expansion
Last modified: 2018-09-04 03:04:50 EDT
Created attachment 1418133 [details] Brick dashboard for not properly managed brick Description of problem: I have tried cluster expansion initiated by a newly added button. Before I pushed the button I waited for some time and opened dashboards. There were created Grafana dashboards for new nodes and bricks that were going to be expanded. Those dashboards were showing no data. Version-Release number of selected component (if applicable): tendrl-ansible-1.6.1-3.el7rhgs.noarch tendrl-api-1.6.1-3.el7rhgs.noarch tendrl-api-httpd-1.6.1-3.el7rhgs.noarch tendrl-commons-1.6.1-3.el7rhgs.noarch tendrl-gluster-integration-1.6.1-3.el7rhgs.noarch tendrl-grafana-plugins-1.6.1-3.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.1-3.el7rhgs.noarch tendrl-node-agent-1.6.1-3.el7rhgs.noarch tendrl-notifier-1.6.0-1.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.1-3.el7rhgs.noarch glusterfs-3.12.2-7.el7rhgs.x86_64 How reproducible: 80% Steps to Reproduce: 1. Setup WA and Gluster cluster with volume. 2. Import cluster into WA. 3. Add more nodes to gluster trusted pool. 4. On new nodes create bricks and add them to existing volume. 5. Run tendrl-ansible on new nodes. 6. Wait half an hour. Actual results: In Grafana are new Host and Brick dashboards for new nodes that show no data (all charts are empty). Expected results: Grafana dashboards for new nodes should be created after cluster expansion triggered by user from UI is finished. Additional info:
This issue si fixed
The issue is fixed for `Host Dashboard` but for `Brick Dashboard` the issue still remains. There are created new options in navigation for `Brick Dashboard` that lead to empty dashboards for unmanaged nodes. --> ASSIGNED Tested with: 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-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
https://github.com/Tendrl/node-agent/pull/811 this patch is not merged in tendrl-node-agent-1.6.3-5.el7rhgs still under review
The issue in `Brick Dashboard` still remains. Not yet expanded node can be selected as `Host Name` option and empty dashboard is shown. --> ASSIGNED 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-5.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-3.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-3.el7rhgs.noarch tendrl-node-agent-1.6.3-5.el7rhgs.noarch tendrl-notifier-1.6.3-3.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-2.el7rhgs.noarch
this issue is wrongly changed to modified state, Please refer above comment, PR for this issue is merged on 21-5-2018. so this changes not in tendrl-node-agent-1.6.3-5.el7rhgs.noarch. It will be in next release.
i have wrongly moved this bug to modified, PR for this issue is merged in upstream, i thought if it is merged then i can move this to modified, but it should in the post. I apologise for this :) i will moving this to post
Looks ok. --> VERIFIED 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