Red Hat Bugzilla – Bug 1583171
Utilization notifications use integration id instead of cluster name
Last modified: 2018-09-04 03:08:06 EDT
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:
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