Adding or editing a schedule outage doesn't reload the configuration for Threshd

Description

Description

From the UI, adding or editing an existing schedule outage for Threshold checking - enabling/disabling a package has no effect on the outage entry in threshd-configuration.xml although the UI reflects the new status. Others such as Notifications, Polling, Data collection reload their respective configuration upon change and therefore new outage entries are updated accordingly. This is the expected behavior but it’s not the case for Thresholds. When in this state, reloading Threshd manually will revert the changes made since it’s loading the configuration that has not been updated.

Workaround

Somehow for some reasons only by deleting a schedule outage from the UI will prompt the outage entries to be updated in threshd-configuration.xml.

Acceptance / Success Criteria

None

Activity

Show:

Alex May April 5, 2023 at 10:15 PM

I was able to recreate the issue as far back as foundation-2020.

PR: https://github.com/OpenNMS/opennms/pull/5958

Fixed

Details

Assignee

Reporter

HB Grooming Date

HB Backlog Status

Sprint

Priority

PagerDuty

Created February 10, 2023 at 9:07 PM
Updated April 6, 2023 at 6:53 PM
Resolved April 6, 2023 at 6:53 PM

Flag notifications