Bug 1589765
Summary: | Volume deleted but still shows up on the Grafana dashboard | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Filip Balák <fbalak> | ||||
Component: | web-admin-tendrl-monitoring-integration | Assignee: | gowtham <gshanmug> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | sds-qe-bugs | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rhgs-3.4 | CC: | rhs-bugs, sankarshan | ||||
Target Milestone: | --- | Keywords: | Regression | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-06-12 07:14:51 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: | 1574938 | ||||||
Attachments: |
|
*** This bug has been marked as a duplicate of bug 1518610 *** |
Created attachment 1449957 [details] Dashboard with deleted volume Description of problem: Volume name stays on grafana Volume and Brick dashboards when it is deleted. Version-Release number of selected component (if applicable): 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 How reproducible: 100% Steps to Reproduce: 1. Import cluster into WA. 2. Created volume in the cluster. This can be done before or after import. 3. Wait until there is information about the volume in grafana. 4. Delete volume: gluster volume <volume-name> stop gluster volume <volume-name> delete 5. Open volume and brick grafana dashboards. Actual results: The volume is still listed listed as Volume Name option. Expected results: The volume should be removed from Grafana. Additional info: