Created attachment 1438759 [details] Screenshot Description of problem: Duplicate Events are Processed and displayed in UI Version-Release number of selected component (if applicable): tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-2.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-3.el7rhgs.noarch tendrl-ansible-1.6.3-4.el7rhgs.noarch tendrl-notifier-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-5.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-3.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-node-agent-1.6.3-5.el7rhgs.noarch How reproducible: 1-1 Steps to Reproduce: 1. Import a cluster into tendrl 2. Extend the cluster with new node using CLI 3. See the Events page in UI. "Peer XXX in cluster XXXXX is Connected" event is displayed from as many as no of peers in the cluster 4. Also note that Cluster integration id is diplayed in the events info even though there is cluster name associated with the specific cluster. this also needs to be fixed Actual results: 1) Duplicate events are displayed 2) event info contains integration_id Expected results: 1) No duplicates 2) event info should contain the cluster name if available
Pr is under review https://github.com/Tendrl/node-agent/pull/817, https://github.com/Tendrl/gluster-integration/pull/649
There is currently no event `Peer XXX in cluster XXXXX is Connected` during expand. It should be according to the screenshot before `New peers identified in cluster` event. Is this expected behaviour now?
As per new change, we are not raising peer connected event during expand, because still that node is not managed by tendrl, So better we should not consider alert or any event for the unmanaged node. Why i am saying this means in grafana also we are not showing brick details or not details for that new node. We will monitor the after expand done for new node or nodes. After that we are raising peer connected disconnected event and alerts for that node.
In BZ 1571755 was resolved problem with `Peer XXX in cluster XXXXX is Connected` that there is not displayed cluster name. `Peer XXX in cluster XXXXX is Connected` event is currently not shown for unmanaged nodes as stated in Comment 7 but it can be triggered by restarting nodes and events related to this are shown only one time. --> VERIFIED Tested with: tendrl-ansible-1.6.3-5.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-7.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-5.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-5.el7rhgs.noarch tendrl-node-agent-1.6.3-7.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-4.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