Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1575040 - Alert dashbaord is not raising alert when cluster is import with shortname
Alert dashbaord is not raising alert when cluster is import with shortname
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: web-admin-tendrl-monitoring-integration (Show other bugs)
3.4
Unspecified Unspecified
unspecified Severity unspecified
: ---
: RHGS 3.4.0
Assigned To: gowtham
Filip Balák
:
Depends On:
Blocks: 1503137
  Show dependency treegraph
 
Reported: 2018-05-04 11:35 EDT by gowtham
Modified: 2018-09-04 03:06 EDT (History)
6 users (show)

See Also:
Fixed In Version: tendrl-ui-1.6.3-2.el7rhgs tendrl-ansible-1.6.3-4.el7rhgs tendrl-notifier-1.6.3-3.el7rhgs tendrl-commons-1.6.3-5.el7rhgs tendrl-api-1.6.3-3.el7rhgs tendrl-monitoring-integration-1.6.3-3.el7rhgs tendrl-node-agent-1.6.3-5.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-09-04 03:05:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github Tendrl/monitoring-integration/issues/442 None None None 2018-05-04 11:36 EDT
Red Hat Product Errata RHSA-2018:2616 None None None 2018-09-04 03:06 EDT

  None (edit)
Description gowtham 2018-05-04 11:35:25 EDT
Description of problem:

If the cluster is imported without a name then monitoring-integration is raising alerts but if the cluster is imported using name then monitoring-integration is unable to raise the alerts. 

Version-Release number of selected component (if applicable):


How reproducible:
Import cluster using some name and increase any resource utilization above 75%. No alerts raised by tendrl for threshold breach.

Steps to Reproduce:
1. Import cluster using a name
2. increase some resource utilization above 75% (cpu or memory or brick or volume)
3. no alerts raised.

Actual results:
Tendrl is not raising utilization alerts.

Expected results:

Tendrl has to raise alerts when a resource threshold breached

Additional info:
Comment 6 Filip Balák 2018-05-28 08:05:29 EDT
Alerts are raised --> VERIFIED
but notifications use integration id instead of cluster name as described in BZ 1583171.

Tested with:
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
Comment 8 errata-xmlrpc 2018-09-04 03:05:38 EDT
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.