Module: check_mk
Branch: master
Commit: 10c9da078fe8a3c1fe49df01ec4dea9e6138a5c5
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=10c9da078fe8a3…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Thu Feb 7 16:28:51 2013 +0100
Updated bug entries #0898
---
.bugs/898 | 21 +++++++--------------
1 files changed, 7 insertions(+), 14 deletions(-)
diff --git a/.bugs/898 b/.bugs/898
index 434e964..4fecb31 100644
--- a/.bugs/898
+++ b/.bugs/898
@@ -1,16 +1,9 @@
-Title: Unresolvable host prevents loading configuration (bad behaviour)
-Component: core
+Title: Make "site" infos available e.g. as group header in "Events
..." views
+Component: ec
State: open
-Date: 2013-01-22 09:44:36
-Targetversion: 1.4.0
-Class: nastiness
+Date: 2013-02-07 16:27:32
+Targetversion: 1.2.2
+Class: cleanup
-It seems strange, I am able to add a host to Check_MK by the host name and
-while the name can be resolved everything is OK. But once the name is not
-resolvable anymore (for whatever reason), the monitoring still works but
-if I want to rewrite the config and restart nagios, the process is blocked
-by that unresolvable host.
-
-This seems a bit nasty. It would be better to have a warning message or just
-no message while applying the config. The monitoring will show me the fact
-that the host is not resolvable.
+The hostname and so on are available and filled, the "site" info can be
selected
+for the view, but there is no data rendered for the site. Should be added.