We came upon the following issue:

1. We set a node in a scheduled outage of type weekly and chose "tuesday" as the day.

2. We stopped a service on the node which was monitored after the node was set in a scheduled outage.

3. After 5 minutes the node created a event and alarm which was about the shutdown service in the previous step.

Also, if i view the schedule in the web ui i can see that the value "null" is applied where "tuesday" should be. What could be affecting this?

I thought it could be that we changed the parameter "org.opennms.ui.datettimeformat" in opennms.properties but i tried disabling our custom format and restarting opennms but that proved to have no effect since it still showed the day as "null".

The second image shows the "Last Updated" which also seems to be missbehaving. For reference we've set the parameter "org.opennms.ui.datettimeformat" to the following:

org.opennms.ui.datettimeformat=MMM d', 'yyyy HH':'mm':'ss

Let me know if you need any more help.

EDIT: I tried to use the "specific" schedule type list the outage via date and time, but again the node creates events & alarms when the service goes down.