Bug 1583171 - Utilization notifications use integration id instead of cluster name
Summary: Utilization notifications use integration id instead of cluster name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-notifier
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.4.0
Assignee: Anmol Sachan
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1503137
TreeView+ depends on / blocked
 
Reported: 2018-05-28 11:55 UTC by Filip Balák
Modified: 2018-09-04 07:08 UTC (History)
5 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:07:10 UTC
Embargoed:

Attachments (Terms of Use)
Events page with alerts (137.75 KB, image/png)
2018-05-28 11:55 UTC, Filip Balák 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github Tendrl monitoring-integration issues 470 0 None None None 2018-05-28 18:01:58 UTC
Red Hat Bugzilla 1575040 0 unspecified CLOSED Alert dashbaord is not raising alert when cluster is import with shortname 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2018:2616 0 None None None 2018-09-04 07:08:05 UTC

Internal Links: 1575040

Description Filip Balák 2018-05-28 11:55:31 UTC 
Created attachment 1443113 [details]
Events page with alerts

Description of problem:
Notifications related to the host cpu and memory utilization use `integration id` instead of `cluster short name` when the Cluster Name is set during import. These ids are in alerts and events.

Version-Release number of selected component (if applicable):
tendrl-ansible-1.5.4-7.el7rhgs.noarch
tendrl-api-1.5.4-4.el7rhgs.noarch
tendrl-api-httpd-1.5.4-4.el7rhgs.noarch
tendrl-commons-1.5.4-9.el7rhgs.noarch
tendrl-grafana-plugins-1.5.4-14.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.5.4-14.el7rhgs.noarch
tendrl-node-agent-1.5.4-16.el7rhgs.noarch
tendrl-notifier-1.5.4-6.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.5.4-6.el7rhgs.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install tendrl.
2. Import cluster, during import set Cluster Name to `cluster1`.
3. Fill CPU and memory on a host: stress --cpu ${N} --vm 1 --vm-bytes ${M}G where N is the number of cpu of particular machine and M is memory that fills memory and swap of hosts.
4. Stop stress program

Actual results:
In Events page for the cluster and in alerts are messages containing cluster id.

Expected results:
All messages should address the cluster by its cluster name `cluster1`.

Additional info:
Comment 4 Filip Balák 2018-06-05 08:07:39 UTC 
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
Comment 6 errata-xmlrpc 2018-09-04 07:07:10 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.