[checkmk-commits] Updated bug entries #2171, #2173, #2283, #2175

Module: check_mk Branch: master Commit: 56399dc45e59e8ccd3fcbd91a6a0e8e5e8b0396e URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=56399dc45e59e8… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Tue Jan 19 15:31:28 2016 +0100 Updated bug entries #2171, #2173, #2283, #2175 --- .bugs/2171 | 7 +++++-- .bugs/2173 | 6 +++++- .bugs/2175 | 14 +++++++++++--- .bugs/2283 | 17 ++++++++++++----- 4 files changed, 33 insertions(+), 11 deletions(-) diff --git a/.bugs/2171 b/.bugs/2171 index f2f17ab..689561e 100644 --- a/.bugs/2171 +++ b/.bugs/2171 @@ -1,7 +1,10 @@ Title: windows agent: able to handle extensions with 2 characters (.py) Component: checks -State: open +Class: bug +State: works4me Date: 2015-03-03 13:23:38 Targetversion: future -Class: bug + +2016-01-19 14:04:13: changed state open -> works4me +Should meanwhile work. diff --git a/.bugs/2173 b/.bugs/2173 index 27a51af..694a51f 100644 --- a/.bugs/2173 +++ b/.bugs/2173 @@ -2,7 +2,7 @@ Title: WATO backup: Do not save configuration files which are derived from omd c Component: wato State: open Date: 2015-03-10 11:30:33 -Targetversion: 1.2.7 +Targetversion: 1.2.9 Class: bug Example: @@ -17,3 +17,7 @@ Fix: OMD configuration into a info file - Upon snapshot restore, each backup domain checks if the requirements of this info file are fulfilled. If not, it raises a warning and the snapshot can not get applied. + + +Hm. This whole WATO backup/snapshot system is broken. We need to find a more clean +solution to all. diff --git a/.bugs/2175 b/.bugs/2175 index 34f2431..e7516dd 100644 --- a/.bugs/2175 +++ b/.bugs/2175 @@ -2,7 +2,7 @@ Title: DropdownChoice: Selects incorrect value if the list of options changes Component: multisite State: open Date: 2015-07-02 09:36:51 -Targetversion: 1.2.7 +Targetversion: 1.2.8 Class: bug 1) Go to BI Rule editor @@ -10,5 +10,13 @@ Class: bug 3) Modifiy the rules in the background, create new, move rule, etc. 4) Observe that wrong selection is stored -Reason: The DropdownChoice valuespec uses the element number to identifiy an element -If this number changes in the background the selection will be wrong +Reason: The DropdownChoice valuespec uses the element number to identifiy +an element If this number changes in the background the selection will be wrong + +Problem: since DropdownChoice can be used to edit arbitrary keys - not just +strings, we cannot use other keys then these integers. In order to prevent +users from storing unintended data we could create a checksum over the combined +text that is displayed in the dropdown (i.e. the titles of the choices). +We ship that in an URL variable. If that is present and does not match the +actual choices then we can issue a MKUserError and the user must select +again. diff --git a/.bugs/2283 b/.bugs/2283 index 735590e..b06b3a0 100644 --- a/.bugs/2283 +++ b/.bugs/2283 @@ -1,10 +1,17 @@ -Title: logwatch: log entries with braces in names can not be shown in logwatch GUI +Title: logwatch: several special characters will break links from logwatch icon Component: multisite -State: open +Class: bug +State: done Date: 2014-12-12 17:21:28 Targetversion: 1.2.7 -Class: bug -Braces are not removed from logwatch stored files. Logwatch-GUI does not -handle this difference correctly. e.g. mk_sap creates such logwatch files +Brackets and quites and some other characters can be part of logfile names +and thus appear in the paths below var/check_mk/logwatch. In the service +descriptions these characters are removed. This the icon pointing to the +logwatch GUI does not work. E.g. mk_sap creates such logwatch files. + +Solution cannot be renaming the stored logfiles. Better would be, if the +GUI more intelligently can find the actual files. +2016-01-19 15:31:11: changed state open -> done +Should work now. Files are now intelligently been found.