When new peer probe is done then all nodes raises peer connected info
event, so multiple events are displayed in UI. As per logic in
https://github.com/Tendrl/node-agent/pull/817 first non-info alert
raised then it will start comparing with an old alert to avoid duplicate
events but here actually info alert is raised first, so node-agent handler
does not have any old alert to avoid duplicate. And also we have a check to
avoid first info alert but it is wrong None == "" won't match.
I have corrected the logic here.
When new peer probe is done then all nodes raises peer connected info event, so multiple events are displayed in UI. As per logic in https://github.com/Tendrl/node-agent/pull/817 first non-info alert raised then it will start comparing with an old alert to avoid duplicate events but here actually info alert is raised first, so node-agent handler does not have any old alert to avoid duplicate. And also we have a check to avoid first info alert but it is wrong None == "" won't match. I have corrected the logic here.
bugzilla: 1579937 tendrl-bug-id: Tendrl/gluster-integration#648
Signed-off-by: GowthamShanmugasundaram gshanmug@redhat.com