From ed90e4aa62ac80cd56a6f6aa04a164e08be00ca6 Mon Sep 17 00:00:00 2001 From: Timotheus Bachinger Date: Tue, 14 Nov 2023 16:21:15 +0100 Subject: [PATCH] Revert "16145 FIX "Always up" hosts can always notify" It seems it breaks the integration tests with: Exception: Did not find '] SERVICE NOTIFICATION: check-mk-notify;notify-test;Check_MK;CRITICAL;check-mk-notify;FAKE CRIT' in var/check_mk/core/history after 20 seconds https://ci.lan.tribe29.com/job/checkmk/job/2.2.0/job/test-integration-single/1510/testReport/junit/pytest.tests.integration.notifications/test_simple_rbn/test_simple_rbn_service_notification/ This reverts commit 59ae761e146139ed09202292ebbcf66b4b953482. --- .werks/16145 | 17 ----------------- 1 file changed, 17 deletions(-) delete mode 100644 .werks/16145 diff --git a/.werks/16145 b/.werks/16145 deleted file mode 100644 index 4987825b51a..00000000000 --- a/.werks/16145 +++ /dev/null @@ -1,17 +0,0 @@ -Title: "Always up" hosts can always notify -Class: fix -Compatible: compat -Component: core -Date: 1699884551 -Edition: cee -Knowledge: undoc -Level: 1 -State: unknown -Version: 2.2.0p15 - -Do not postpone notifications for "always up" hosts. - -The notification logic would wrongly assume that "always up" hosts may, -in fact, be down and erroneously postpone notifications. This has been -fixed, such hosts are never down. -