Module: check_mk
Branch: master
Commit: 53a2782396daaa4ce40abd16f763512280dd7bc6
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=53a2782396daaa…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Fri Oct 27 09:28:54 2017 +0200
Updated bug entries #2498, #2555
Change-Id: I4fc823c5d5e133906b48ff13f3addacd155e0190
---
.bugs/2498 | 7 +++++--
.bugs/2555 | 7 +++++--
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/.bugs/2498 b/.bugs/2498
index e8a5e1f..1f0e2c5 100644
--- a/.bugs/2498
+++ b/.bugs/2498
@@ -1,9 +1,9 @@
Title: WATO-Snapshots should warn if data in local/ is too much
Component: wato
-State: open
+Class: bug
+State: done
Date: 2016-07-06 11:43:10
Targetversion: 1.5.0
-Class: bug
We had the case that a user pu approx 4GB of tmp data below local/.
During "Activate Changes" WATO creates a snapshot of this. This
@@ -17,3 +17,6 @@ limit? Or positively check all directories?
Solution: We are planning to create some "todo / config and performance hints"
page that shows a list of things to tune to have a good setup. This page could
make such a local/ directory size check.
+
+2017-10-27 08:51:48: changed state open -> done
+This will be part of the upcoming best practices tests.
diff --git a/.bugs/2555 b/.bugs/2555
index f3c39e5..f00bb1f 100644
--- a/.bugs/2555
+++ b/.bugs/2555
@@ -1,11 +1,14 @@
Title: Match for contact groups when core = Nagios does not work
Component: notification
-State: open
+Class: bug
+State: works4me
Date: 2017-06-08 08:10:56
Targetversion: 1.4.0
-Class: bug
When doing notification rules with matching on contact groups
we need the list of contactgroups from the core. These doe
not seem to be present when the core is Nagios so we need
to fetch them via Livestatus. This is not yet implemented.
+
+2017-10-27 08:42:37: changed state open -> works4me
+Seems this has been implemented in the meantime. It works as intended.
Module: check_mk
Branch: master
Commit: 06fb9b763a57c1aaf40948fb46988263a92467b5
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=06fb9b763a57c1…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Fri Oct 27 10:42:26 2017 +0200
Fixed possible exception related to "tmp_path" vari able in case of locking issues during saving
Change-Id: Ib9f61097dd04176ed77a1836a2cb917529a70012
---
lib/store.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/store.py b/lib/store.py
index f88545d..5efbc45 100644
--- a/lib/store.py
+++ b/lib/store.py
@@ -154,13 +154,14 @@ def save_data_to_file(path, data, pretty=True):
# Then the new file is written to a temporary file and moved to the target path
def save_file(path, content, mode=0660):
try:
+ tmp_path = None
+
# Normally the file is already locked (when data has been loaded before with lock=True),
# but lock it just to be sure we have the lock on the file.
#
# Please note that this already creates the file with 0 bytes (in case it is missing).
aquire_lock(path)
- tmp_path = None
with tempfile.NamedTemporaryFile("w", dir=os.path.dirname(path),
prefix=".%s.new" % os.path.basename(path),
delete=False) as tmp: