ID: 5797
Title: netapp_api_luns: fixed interchanged free/used names in WATO configuration rule
Component: WATO
Level: 1
Class: Bug fix
Version: 1.5.0i4
The levels configuration for netapp_api_luns was incorrectly named.
The free space levels were treated as used space and vice versa.
ID: 5931
Title: Fixed "skipping unimplemented check" warning message of active checks
Component: WATO
Level: 1
Class: Bug fix
Version: 1.5.0i4
If an active check was disabled via the rule "Disabled services"
and then readmitted to the list of monitored services of the host
on the service discovery page, this active check was falsely stored
to the related autochecks file which caused above warning message.
ID: 5941
Title: Fixed nagios using outdated config when not using "cmk -R/-O"
Component: Other Components
Level: 1
Class: Bug fix
Version: 1.5.0i4
When using "omd start/restart" or the init script etc/init.d/nagios to
start or restart nagios, it was possible that the core started with an
outdated configuration.
During start/restart the nagios init script is working in two steps: 1. config
validation and 2. start/restart of the nagios process. During both steps the
whole object configuration (etc/nagios/conf.d) needs to be processed. To
optimize this the first step is perfoming some precompiling of the read config
files. The result is saved in the file var/nagios/objects.precache and read
by the core during startup instead of the single object config files.
The init script had an option set (CORE_NOVERIFY=yes) in all cases that
prevented the config verification even when executed manually. Without the
config verification the object precache was not updated before the restart,
making the core load an outdated file. The variable CORE_NOVERIFY=yes should
only be set when the config verification has already been done. For example cmk
-R/-O is doing exactly this.
A workaround is to trigger the restarts using "cmk -R".
ID: 5940
Title: Fixed broken packaging of CME in 1.5
Component: Other Components
Level: 1
Class: Bug fix
Version: 1.5.0i4
The error "Configuration Error: 'module' object has no attribute 'current_customer'" occured while
creating the core configuration for sites created with 1.5.
ID: 5796
Title: Fixed race condition in counter computation if a host uses real time checks
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
There was a risk that the counter data for the Check_MK checks could get lost or reset
to an earlier state, when the host received regular updates through the realtime check mechanism.
This has been fixed. As a side effect, the counter data is now only saved back to disk when there were
actual changes.
ID: 5920
Title: Windows: use standard file matching patterns for fileinfo
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
Until now, Windows agent was using a non-standard way of defining recursive
wildcards. From now on, the supported wildcard patterns '*', '?' and '**' work
in a standardized way. Recursive patterns can be defined with '**', matching
all descendants of the path so far. Previous patterns with single '*'s on
several directory levels will from now on work as non-recursive patterns
conforming to the standard.
ID: 5912
Title: mk_jolokia: Fixed exception in Bakery rule if an instance is set
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
A typo prevented the bakery ruleset to work correctly and has been introduced
in werk #5762.