Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: Meridian-2015.1.4, Meridian-2016.1.4, 18.0.4, 19.0.0
-
Fix Version/s: 19.0.1, Meridian-2015.1.5, Meridian-2016.1.5
-
Component/s: Polling / Monitors / Outages
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Sprint:Horizon - Feb 15th
Description
We recently experienced an issues where nodeDown events were being generated for a deleted node.
The node had been deleted by synchronizing a provisioning requisition and pollerd logged an error with the following:
2017-02-14 17:41:52,779 ERROR [Poller:PollerEventProcessor-Thread] o.o.n.p.PollerEventProcessor: Interface 226/192.81.216.28 does not exist in pollable node map, unable to delete node. 2017-02-14 17:41:52,782 ERROR [Poller:PollerEventProcessor-Thread] o.o.n.p.PollerEventProcessor: Interface 226/10.10.0.6 does not exist in pollable node map, unable to delete node. 2017-02-14 17:41:52,784 ERROR [Poller:PollerEventProcessor-Thread] o.o.n.p.PollerEventProcessor: Interface 226/10.0.0.200 does not exist in pollable node map, unable to delete node. 2017-02-14 17:41:52,787 ERROR [Poller:PollerEventProcessor-Thread] o.o.n.p.PollerEventProcessor: Nodeid 226 does not exist in pollable node map, unable to delete node.
However, the node continued to be polled:
2017-02-15 14:10:54,726 INFO [Poller-Thread-15-of-30] o.o.n.p.p.PollableElement: Changing status of PollableElement PollableInterface [PollableNode [226]:192.81.216.28] from Down to Up