ID: 6579
Title: Fixed host renaming in notification rules
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
Under certain circumstances, it was possible that hosts in notification
rules of a user were not rewritten during host renaming. This has been
fixed.
ID: 6569
Title: mk_logwatch: options are no longer applied globally
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Until this fix, a specified option had overwritten any previously defined values
for said option, and was applied globally.
This has now been fixed: The scope of an option is limited to the files on the same line.
In case the same file is referenced in different lines, the options for this specific
file are updated with the new ones, keeping the allready defined ones.
ID: 6550
Title: Fixed warning "bad ps syntax" when stopping a site on e.g. SLES11
Component: Site Management
Level: 1
Class: Bug fix
Version: 1.6.0i1
When using older ps versions like procps 3.2.7, which is used e.g. on SLES11, a warning message
like this was displayed when executing "omd stop" on a site:
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
Stopping 1 remaining site processes...OK
ID: 6549
Title: Crash reports: Filter out password/_password from HTTP vars of GUI crashes
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
When a crash occurs during the login procedure where a user entered his password during
verification of this password, the crash could contain this password in plain text in
the HTTP variable data structure. The vars named password/_password are now explicitly
filtered to prevent this.
ID: 6475
Title: New Theme: Fixed snapins in dashboards
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
The layout of snapins is slightly different if embedded into dashboards for
a more proper look.
ID: 6484
Title: Fixed filtering check plugins for the management board and the host itself
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
In order to decide which check is used for which data source
we have to filter the found check plugins. This is done via
the check_info key "management_board". There are three values
with the following meanings:
- MGMT_ONLY
These check plugins
- are only used for management board data sources,
- have the prefix 'mgmt_' in their name,
- have the prefix 'Management Interface:' in their service description.
- If there is an equivalent host check plugin then it must be 'HOST_ONLY'.
- HOST_PRECEDENCE
- Default value for all check plugins.
- It does not have to be declared in the check_info.
- Special situation for SNMP management boards:
- If a host is not a SNMP host these checks are used for
the SNMP management boards.
- If a host is a SNMP host these checks are used for
the host itself.
- HOST_ONLY
These check plugins
- are used for 'real' host data sources, not for host management board data sources
- there is an equivalent 'MGMT_ONLY'-management board check plugin.
Migration from 1.4 to 1.5:
in 1.4 TCP hosts with SNMP management boards discovered TCP and
SNMP checks, eg. uptime and snmp_uptime. During checking phase
these checks should be executed
further on.
In versions >= 1.5 there are management board specific check
plugins, eg. mgmt_snmp_uptime.
After a re-discovery Check_MK finds the uptime check plugin for
the TCP host and the mgmt_snmp_uptime check for the SNMP
management board. Moreover Check_MK eliminates 'HOST_ONLT'
checks like snmp_uptime.
ID: 6501
Title: Warn during config generation when an unknown timeperiod from a shadow host is encountered.
Component: config
Level: 1
Class: Bug fix
Version: 1.6.0i1
When a shadow host uses a timeperiod which is unknown on the master site, we
issue a warning during config generation time ("cmk -U" etc.) now. We
substitute the timeperiod "24X7" (i.e. "Always") in these cases.
ID: 6530
Title: Fixed possible error "You can not override a builtin auxiliary tag" after update
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
During the tag migration from 1.5 or newer a problem could happen that the auxiliary
tags "snmp" and "tcp" were not removed correctly. This happened when the titles of these
auxiliary tags have been changed in the site.
This is a regression since 1.5.0p1 (caused by #6247).
Workaround with 1.5.0p2 or older: Have a look at the
/omd/sites/[SITE]/etc/check_mk/multisite.d/wato/hosttags.mk file. First create
a backup of this file, then look for entries like this:
wato_aux_tags += \
[('snmp', u'monitor via SNMP'), ('tcp', u'monitor via Check_MK Agent')]
Try to remove the line and reload the GUI. The issue should be gone now.