4.4.2 - Still a state issue SOFT/HARD and notifications

[void64]

We noticed and reported a bug with 4.4.1 having to do with services/hosts going into a soft state and then staying stuck in that state, so if a service/host went down we would get the recovery, but if it went back down we'd never get it again as it was stuck in a soft state.

Seems like it was "fixed" in 4.4.2 with creating a hard recovery, but now a new problem.

We're now getting SERVICE/HOST going into a soft state and they are triggering warnings.... for the SOFT, ok, we get it. But it's a SOFT state when the recovery hits, it's HARD. So the result it, we don't get the warning (expected), but we get notifications on the OK's.. (not expected). So we're getting erroneous notifications .. another bug or is there a workaround/change we need? Behavior was fine pre 4.4.1/4.4.2


[09-09-2018 10:58:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;OK;HARD;1;SNMP OK - 5050 VAC
Service Warning[09-09-2018 10:57:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;WARNING;SOFT;1;SNMP WARNING - *5057* VAC
Service Ok[09-09-2018 10:53:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;OK;HARD;1;SNMP OK - 5047 VAC
Service Warning[09-09-2018 10:52:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;WARNING;SOFT;1;SNMP WARNING - *5052* VAC
Service Ok[09-09-2018 10:51:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;OK;HARD;1;SNMP OK - 5050 VAC
Service Warning[09-09-2018 10:50:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;WARNING;SOFT;1;SNMP WARNING - *5054* VAC

[lmiltchev]

This is a known issue - I filed a bug report 11 days ago:

https://github.com/NagiosEnterprises/na ... issues/575

Our developers will be looking into this as soon as they can.