Open Scheduled Outages that pass their end time when OpenNMS is down do not get closed when OpenNMS starts
Description
If a scheduled outage which has started while OpenNMS is running, then passes its end time when OpenNMS happens to be down, when OpenNMS starts after the end of the sheduled outage, the scheduled outage remains enforced even though the outage window has passed.
This causes a loss of monitoring until the outage is manually deleted.
I believe what should be happening here, is that when OpenNMS starts, it should make an immediate check of any currently open scheduled outages to see if the end time has passed, and if so to close the outage.
Note: this may also be an issue when OpenNMS is down when a scheduled outage is supposed to start. However, it is the failure to end completed outages that is the far greater issue here, as this will halt monitoring.
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
John Blackburn April 28, 2020 at 3:52 AM
I've come across situations where the outage did not end even though the OpenNMS server never shutdown.
If a scheduled outage which has started while OpenNMS is running, then passes its end time when OpenNMS happens to be down, when OpenNMS starts after the end of the sheduled outage, the scheduled outage remains enforced even though the outage window has passed.
This causes a loss of monitoring until the outage is manually deleted.
I believe what should be happening here, is that when OpenNMS starts, it should make an immediate check of any currently open scheduled outages to see if the end time has passed, and if so to close the outage.
Note: this may also be an issue when OpenNMS is down when a scheduled outage is supposed to start. However, it is the failure to end completed outages that is the far greater issue here, as this will halt monitoring.