-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 19.1.0
-
Fix Version/s: 20.0.2, Meridian-2017.1.0
-
Component/s: Notifications / Actions, Web UI - Admin
-
Security Level: Default (Default Security Scheme)
-
Labels:
While following the tutorial from the wiki (https://wiki.opennms.org/wiki/Tutorial_Notifications), I figured that when you create a new destination path, the "default" value for the "initial delay" is "null", which didn't happen before. I mean, on Meridian 2016, the default is "0s" (which is a valid value).
This leads to a broken configuration which prevents the notifications to be sent, if you forget to fix it.
- duplicates
-
NMS-9527 Destination path initial-delay parsing causing NumberFormatException
-
- Closed
-