Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 14.0.3, Meridian-2015.1.0, 15.0.2, 17.0.0
-
Fix Version/s: 16.0.3, Meridian-2015.1.1
-
Component/s: Polling / Monitors / Outages
-
Security Level: Default (Default Security Scheme)
-
Labels:None
Description
Notes
Steps to reproduce:
- Create a requisition with a single, reachable node in it and synchronize
- Wait for the node to be polled once successfully
- Remove the polled node from the network so that it enters a node-level outage
- A single nodeDown event is created when the outage is opened
- Add a category to the node in the requisition
- With the node still down, synchronize the requisition
Expected result: A single nodeCategoryMembershipChanged event is created for the node
Actual result: In addition to the expected category-related event, a handful of spurious nodeDown events follow a short time later