Module: check_mk Branch: master Commit: 1c337e5bd06853d04e3a861d45d2013d3027f0a5 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=1c337e5bd06853… Author: Lars Michelsen <lm(a)mathias-kettner.de> Date: Thu Feb 16 17:26:48 2017 +0100 Updated bug entries #2496, #2498, #2507, #2506, #2517 Change-Id: Ief9183af0a18b9b42e8f205479163181647772f3 --- .bugs/2496 | 7 +++++-- .bugs/2498 | 8 +++++++- .bugs/2506 | 8 ++++++-- .bugs/2507 | 8 ++++++-- .bugs/2517 | 9 +++++++-- 5 files changed, 31 insertions(+), 9 deletions(-) diff --git a/.bugs/2496 b/.bugs/2496 index 6e1fd3b..9332ae4 100644 --- a/.bugs/2496 +++ b/.bugs/2496 @@ -1,11 +1,14 @@ Title: Folders snaping -> some subfolder -> dashboards -> Globestatistik -> Link in number wrong Component: multisite -State: open +Class: bug +State: done Date: 2016-06-27 11:53:50 Targetversion: 1.2.8 -Class: bug On a dashboards that shows just a subfolder of WATO the statistics in the globes print the correct numbers. But a click on such a number seems to drop the WATO folder filter so the resulting view is global - not for the selected folder. + +2017-02-16 16:36:44: changed state open -> done +Fixed. diff --git a/.bugs/2498 b/.bugs/2498 index 4f60f1f..e8a5e1f 100644 --- a/.bugs/2498 +++ b/.bugs/2498 @@ -2,7 +2,7 @@ Title: WATO-Snapshots should warn if data in local/ is too much Component: wato State: open Date: 2016-07-06 11:43:10 -Targetversion: 1.2.8 +Targetversion: 1.5.0 Class: bug We had the case that a user pu approx 4GB of tmp data below local/. @@ -11,3 +11,9 @@ took very long and lead to a Apache timeout (proxy error...). We need to validate the data in local/ somehow. Maybe make size 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. diff --git a/.bugs/2506 b/.bugs/2506 index d9b93e3..2dee555 100644 --- a/.bugs/2506 +++ b/.bugs/2506 @@ -1,12 +1,16 @@ Title: Rule Disabled Services only work with positive result Component: wato -State: open +Class: bug +State: works4me Date: 2016-08-03 13:19:26 Targetversion: 1.2.8 -Class: bug You want to disable all Services like MSSQL.* and use one rule with a positive outcome. All services will be disabled. After that rule you add another one and try to get explizit services again like MSSQL Production$. That shoudl work with a negative outcome. It will not work. All combinations do not get the result, that was wished. Disable all services and include only some of them. + +2017-02-16 17:06:32: changed state open -> works4me +Works as expected. The first rule needs to be the "include" rule and the second one +the "exclude" rule. diff --git a/.bugs/2507 b/.bugs/2507 index feca946..b58c7ca 100644 --- a/.bugs/2507 +++ b/.bugs/2507 @@ -1,9 +1,9 @@ Title: clustered services does not filter by hostname Component: wato -State: open +Class: bug +State: works4me Date: 2016-08-10 13:13:00 Targetversion: 1.2.8 -Class: bug Wenn in "Clustered services" eine Regel erstellt wird, welche nur nach einem bestimmten Service auf einem bestimmten Host matchen sollte, greift diese dennoch auf allen Hosts, welche im Cluster sind und den genannten Service haben. Bsp: Host A hat den Service 1 @@ -18,3 +18,7 @@ Die erste Regel fügt den Inhalt der Services 1 von beiden Hosts zu einem Servic Die zweite Regel tut was sie soll, da auf Host A der Service nicht zur Verfügung steht. Der Service des Host B wird allerdings weiterhin als Host B zugeordnet angezeigt und der Service von Host A wird korrekt als "Already configured clustered services" definiert. + +2017-02-16 17:24:48: changed state open -> works4me +Can not reproduce, works as expected. Please let me know how to reproduce in case +this is still an issue. diff --git a/.bugs/2517 b/.bugs/2517 index 56413c9..2bbb7ef 100644 --- a/.bugs/2517 +++ b/.bugs/2517 @@ -1,9 +1,9 @@ Title: Migration from Ubuntu to RedHat with omd backup failed Component: multisite -State: open +Class: bug +State: done Date: 2016-08-17 13:54:17 Targetversion: 1.2.8 -Class: bug If you create a backup of an existing site with omd backup on a Ubuntu server and do a restore on a RedHat machine with omd restore, then the site will not be startet. Apache configuration is @@ -11,3 +11,8 @@ wrong, because during the restore the lokale Apache configuration is not reset t Workaround: Replace the include section of modules with default section of another site. + +2017-02-16 17:26:31: changed state open -> done +This has been fixed with current versions. The files have been made +more portable so that you don't need to change the module paths +anymore.