[checkmk-commits] Updated bug entries #2522, #2524, #2519

Module: check_mk Branch: master Commit: f2646f7bb6a170e845dd731881aadfcc3cc70cf0 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=f2646f7bb6a170… Author: Lars Michelsen <lm(a)mathias-kettner.de> Date: Fri Feb 17 11:30:17 2017 +0100 Updated bug entries #2522, #2524, #2519 Change-Id: Ie6eca10515923eda8c56c3c397bc565c2adf8497 --- .bugs/2519 | 10 ++++++++-- .bugs/2522 | 8 ++++++-- .bugs/2524 | 10 ++++++++-- 3 files changed, 22 insertions(+), 6 deletions(-) diff --git a/.bugs/2519 b/.bugs/2519 index 1f7b49c..b1dcba3 100644 --- a/.bugs/2519 +++ b/.bugs/2519 @@ -1,10 +1,16 @@ Title: Input field of hostname is not a regex input field in configuration rules Component: wato -State: open +Class: bug +State: done Date: 2016-08-17 19:23:41 Targetversion: 1.2.8 -Class: bug If you create a new rule in WATO for configuration and want to use regex to match hostnames you have to add the ~(tilde) in front of the hostname to get regex matching. This inout field should be a regex input field as default. + +2017-02-17 11:11:32: changed state open -> done +This is impossible for us to change. What we are planning to do for the 1.5 release +is to visualize the type of the fields better to make the user know which kind of +field he has to fill and to give the user an option to switch the mechanics from +exact host name matching to regex matching by clicking an icon on that field. diff --git a/.bugs/2522 b/.bugs/2522 index 1722aca..8c30412 100644 --- a/.bugs/2522 +++ b/.bugs/2522 @@ -1,9 +1,9 @@ Title: Distributed Monitoring: User action breaks configuration Component: multisite -State: open +Class: bug +State: done Date: 2016-10-25 12:10:19 Targetversion: 1.2.8 -Class: bug The user is using a distributed monitoring setup with central WATO configuration. The slave sites are only monitoring a part of the hosts configured on the master and @@ -24,3 +24,7 @@ Workaround: Please modify global settings of affected slave sites. Edit and save without any change. After the activation, all slave sites will be updated to the correct configuration. If the duplicated hosts does not disappear, please login to the slave and do a cmk -R as site user. + +2017-02-17 11:05:19: changed state open -> done +This has already been fixed by dealing correctly with the hosts that are not assigned to that +site. These hosts will not be monitored by the slave site anymore. diff --git a/.bugs/2524 b/.bugs/2524 index 7332c5c..8e9fa22 100644 --- a/.bugs/2524 +++ b/.bugs/2524 @@ -1,9 +1,9 @@ Title: Distributed Monitoring: Micro Core does need a restart instead of reload to activate the changes Component: core -State: open +Class: bug +State: works4me Date: 2016-10-25 12:29:16 Targetversion: 1.2.8 -Class: bug The user is using a distributed monitoring setup with central WATO configuration. The slave sites are only monitoring a part of the hosts configured on the master and @@ -17,3 +17,9 @@ Master and two slave sites. Add some hosts on the Mater site and put add those h Make some changes on the slave site. Those hosts will be duplicated in the global monitoring. If you edit the global site settings and make the activation, the hosts does not disappear. Only a cmk -R on the slave site will fix it. The correct configuration is applied, but will not be actived for monitoring. + +2017-02-17 11:09:59: changed state open -> works4me +Can not reproduce this with current 1.2.8. Would need more detailed information +on which changes have been made in which step. For it works as expected. The +host that has been configured on the slave site is removed from the sites config +during sync and replaced by the config received from the master.