ID: 14103
Title: Fix synchronisation of password store entries to customer sites
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
This werk fixes two problems:
The ValueError that was fixed for other editions in werk #14102.
The password store entries were always completly synchronised to the remote
sites. The customer option that should be used for calculating the passwords to
synchronize was ignored.
ID: 14102
Title: Fix possible ValueError on activation of remote sites
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
If the password store was used in distributed environments, the error
"ValueError: MAC check failed" could occur on activation of remote sites.
ID: 14085
Title: Bring back support of StorCLI on Linux to monitor megaraid controllers
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Newer versions of the StorCLI tool no longer supported the commands used by MegaCLI to monitor physical and virtual disks.
The agent now uses the successor commands to generate dedicated sections, bringing back the check plugins <tt>megaraid_pdisks</tt> and <tt>megaraid_ldisks</tt>.
ID: 14082
Title: megaraid_ldisks: configurable via "LSI RAID logical disks"
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
In an effort to make the RAID monitoring more consistent, the
plugin megaraid_ldisks now is configurable using the ruleset
<i>LSI RAID logical disks</i>.
ID: 14081
Title: megaraid_pdisks: configurable via "LSI RAID physical disks"
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
In an effort to make the RAID monitoring more consistent, the
plugin megaraid_pdisks now is configurable using the ruleset
<i>LSI RAID physical disks</i>.
ID: 13850
Title: megaraid: new service names
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
This werk changes the items and service names of the megaraid plugins.
Existing services will continue to produce correct results, but we encourage users to switch to the new services as soon as possible (see below for details).
Every service discovered by the megaraid plugins will now use the objects identifier as item.
In addition, the service names have been cleaned up.
For instance:
<ul>
<li><i>RAID Adapter/BBU 0</i> becomes <i>RAID BBU /c0</i></li>
<li><i>RAID Adapter/LDisk 0/1</i> becomes <i>RAID logical disk /c0/v1</i></li>
</ul>
Generally, physical disks connected via RAID controllers are identified by their controller, enclosure and slot.
The <tt>storcli</tt> command uses the abbreviations 'c', 'e' and 's', respectively.
However, in the previos version of the plugin, the controller index had been encoded in the first letter of the item:
The 'e' in the physical disks services referred to "the first controller", not to "enclosure".
The second controller has been marked 'f':
<ul>
<li><i>RAID Adapt/Enc/Sl e01/2</i> becomes <i>RAID physical disk /c0/e01/s02</i></li>
<li><i>RAID Adapt/Enc/Sl f03/4</i> becomes <i>RAID physical disk /c1/e03/s04</i></li>
</ul>
While the new item name (e.g. <i>/c0/e0/s1</i> instead of <i>e0/1</i>) will be used for all newly discovered servces, users that upgraded from an older Checkmk version need to enable the new service description using the global sestting "<i>Use new service descriptions</i>".
ID: 14047
Title: inventory_lnx_packages: Fix package version parsing for deb packages
Component: HW/SW Inventory
Level: 1
Class: Bug fix
Version: 2.2.0i1
Package version of deb packages in inventory was always "-". Now,
the package version is correctly parsed from the version.
ID: 14046
Title: inventory_lnx_packages: Fix crash when there is no package version
Component: HW/SW Inventory
Level: 1
Class: Bug fix
Version: 2.2.0i1
Discovery would crash if there was no package version. It would
result with packages not being shown in the Inventory tree.
ID: 14072
Title: Filesystem (<tt>df</tt>) check plugins: Handle zero free inodes correctly
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Most filesystem (<tt>df</tt>) check plugins, such as the plugin for Linux systems,
did not handle the case of exactly zero free inodes correctly. Independently of
the user configuration, no check result at all for the free inodes was reported
in this particular case.