ID: 10031
Title: Warn about editing rules which conditions are not valid anymore
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
When a rule is opened for editing and an the rule edit dialog detected
an invalid previous value, it prints a warning message about this to
the user.
The same is now done for the rule conditions. In case e.g. a rule refers
to a tag group or tag that does not exist (anymore) in the current WATO
configuration, the dialog shows a warning message instead of silently
dropping the invalid option as it was done before.
ID: 8895
Title: Windows Agent supports async local plugins with cache_age
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0b7
Now Windows Agent adds to the output from the local plugin the string
with cache information if the local plugin has cache_age property set
in configuration file.
Thus, the Windows Agent now fully supports the improvements made in the
werk 7402 also for local plugins running asynchronously.
ID: 8898
Title: New command line option 'restore' for Windows Agent
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0b9
This command line option restores original bakery configuration,
which consists from the next elements: check_mk.bakery.yml,
bakery plugins and checkmk.dat.
If installed Windows Agent has no bakery configuration, for example,
packaged agent, then nothing happens.
ID: 8896
Title: Fixed rare crash when a plugin should be terminated
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b8
Previously, in the process of terminating of the hanging plugins,
the Windows Agent could accidentally destroy an important process,
thus causing BSOD.
Since then, the Agent uses a safe algorithm to terminate plugins.
ID: 8897
Title: Plug-in configuration is correctly processed by the agent
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b8
Previously, Windows Agent processed the plugin configuration
using the approach: the first rule wins.
Thus, each plugin can only use one rule for its configuration.
>From now on, the Windows Agent agent applies all the rules to each plugin,
provided that the rule file name pattern matches with the plugin name.
ID: 10055
Title: The Windows Agent service loads correct configuration
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b9
Previously, after installation from MSI, the Windows Agent service loaded
its own configuration too early, thus loading the default(fabric) configuration,
ignoring bakery configuration.
To use the configuration provided by bakery, you should restart the service
manually.
Since now Windows Agent loads the configuration only after updating the
Legacy Agent configuration and after installing the Bakery configuration.
ID: 8899
Title: Windows Agent only_from parameter works now correctly
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b9
Previously in check_mk.user.yml, installed from the Windows Agent MSI,
the parameter 'only_from' was incorrectly initialized with an empty value.
This effectively prevented the setting of 'only_from' using Bakery,
because the user configuration is more prioritized than the bakery one.
Now the 'only_from' parameter is removed from check_mk.user.yml.
ID: 7944
Title: Fixed handling of unfresh services
Component: cmc
Level: 2
Class: Bug fix
Version: 1.7.0i1
The 1.6.0 branch introduced a regression: When a service was detected as
unfresh, the CMC terminated with a log message of the form:
host name mismatch in active check result: expected 'FOO', got 'BAR'
Even worse, this state was permanent: After restarting the same thing
happened again, so the only way to get out of this was to remove the CMC's
state file. Note that this only affected unfresh services, not hosts.
The problem was caused by an internal confusion of host name and service
name of the unfresh service, which has been fixed.
ID: 10028
Title: NagVis maps snapin: Improve error handling
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
The maps snapin showed a crash in case NagVis reported a
an error while producing the map list. The error message
from NagVis is now displayed instead.