Bug 1559405

Summary:	Alerts which is raised from node-agent is not displayed in UI
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	gowtham <gshanmug>
Component:	web-admin-tendrl-node-agent	Assignee:	gowtham <gshanmug>
Status:	CLOSED ERRATA	QA Contact:	Filip Balák <fbalak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	fbalak, mbukatov, nthomas, rhs-bugs
Target Milestone:	---
Target Release:	RHGS 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tendrl-commons-1.6.1-3.el7rhgs	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 07:02:28 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:	1503137

Description gowtham 2018-03-22 13:34:57 UTC

Description of problem:
Any alert which is raised from node-agent is not processed and displayed in UI.
All log messages are pushed into node-agent socket, If the log message is in notice priority then message handler will pass the log message into the alert handler as well as a logger. But node-agent component log messages are directly pushed into logger because of no need to push into the node-agent socket. So no one is pushing notice messages into alert handler. 

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


How reproducible:
Peer probe a new node with the already managed cluster But no alert messages are raised about new node is ready for expansion. 

Steps to Reproduce:
1. 
2.
3.

Actual results:
When a new node is peer probe with already managed cluster then it not raising any alert.

Expected results:
The new alert message should be raised and displayed in UI when new peer probe is happening with a new node.

Additional info:

Comment 4 Filip Balák 2018-05-25 13:26:57 UTC

Reproduced with old version (tendrl-notifier-1.5.4-6.el7rhgs.noarch) and 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-gluster-integration-1.6.3-3.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

When tendrl is not installed on nodes but the nodes are added to managed cluster there is newly shown alert:
```
New peers identified in cluster: <cluster-id>. Make sure tendrl-ansible is executed for the new nodes so that expand cluster option can be triggered
```

Looks ok. --> VERIFIED

Comment 6 errata-xmlrpc 2018-09-04 07:02:28 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