Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

initial-delay="null" when adding a new destination path

Description

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.

Acceptance / Success Criteria

None

Attachments

1
  • 31 Jul 2017, 06:20 PM

Lucidchart Diagrams

Activity

Show:

Alejandro Galue July 31, 2017 at 6:16 PM

If you're using 19.1.0, the fix from the PR won't work, here is a usable fix for that version of OpenNMS. On /opt/opennms/jetty-webapps/opennms/admin/notification/pathOutline.jsp, around line 182, add the following logic for getInitialDelay():

<div class="form-group"> <label for="input_initialDelay" class="control-label col-sm-2">Initial Delay:</label> <div class="col-sm-10"> <%=buildDelaySelect(intervals, "initialDelay", newPath.getInitialDelay() == null ? "0s" : newPath.getInitialDelay())%> </div> </div>

Alejandro Galue July 31, 2017 at 6:15 PM

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created July 31, 2017 at 4:50 PM
Updated August 9, 2017 at 5:38 PM
Resolved August 2, 2017 at 3:20 PM

Flag notifications