ID: 14851
Title: Improve performance of "Archive events" actions
Component: Event Console
Level: 1
Class: New feature
Version: 2.2.0i1
This change makes the "Archive events" actions in the
Event Console faster and more reliable.
This concerns both the selected events and all events of one host.
Especially if you have remote sites configured,
since there is no more query round-trip.
ID: 14628
Title: 3par_ports: Check and discovery used to fail if the protocol was NVMe
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The discovery and check functions used to crash because the port protocol was NVMe.
Now the check support the following protocols:
<ul>
<li>FC</li>
<li>iSCSI</li>
<li>FCOE</li>
<li>IP</li>
<li>SAS</li>
<li>NVMe</li>
</ul>
ID: 14844
Title: One hash file per package
Component: Other Components
Level: 1
Class: New feature
Version: 2.2.0i1
The HASHES file is split into one PACKAGE_NAME.PACKAGE_EXTENSION.hash file per package.
ID: 14740
Title: postgresql_stat_database: Levels for PostgreSQL database size
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
It's now possible to set CRIT/WARN levels on the size of PostgreSQL databases.
This can be configured at the ruleset <i>PostgreSQL Database Statistics</i> and has
effect to the state of the <i>PostgreSQL DB .. size</i> service.
ID: 14650
Title: mk_job: No longer mount volumes on monitored hosts
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
We recently observed problems on Checkmk appliances caused by the agent mounting volumes.
This was in turn caused by the section responsible to output the statistics created by the <tt>mk-job</tt> wrapper.
For every existing <tt>/var/lib/check_mk_agent/job/[USER]</tt> folder, the agent started a login shell for <i>USER</i>.
This in turn made systemd automatically mount a volume under certain circumstances.
The agents use of <tt>su</tt> was a measure to prevent symlink and hardlink attacks -- this is now done differently, without the use of <tt>su</tt>.
ID: 13434
Title: Fix 500 status when deleting non existing downtimes
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
It was possible that checkmk returned an error message like "Permission
mismatch. See the server logs for more information." when trying to delete a
non existing downtime.
ID: 14386
Title: Recommend using htpasswd with bcrypt
Component: Site Management
Level: 1
Class: New feature
Version: 2.2.0i1
The welcome message displayed by <tt>omd create</tt> now recommends setting the password for cmkadmin using <tt>htpasswd -B -C 12</tt>.
This way htpasswd will use bcrypt with a work factor of 12 instead of MD5 to hash the password, which is consistent with the behavior when setting passwords in WATO.
ID: 14649
Title: Extension packages: Support different versions in distributed setups
Component: Setup
Level: 1
Class: New feature
Version: 2.2.0i1
This feature affects users that maintain a distributed setup where not all sites run the same Checkmk version.
Users can now simultaneously manage conflicting MKPs for different Checkmk versions.
MKPs that are uploaded to a site can now have one of three states:
<b>Available:</b>
The MKP is uploaded to the site.
It is not even unpacked, it just sits on disk.
Every MKP will be shown in this list, regardles of its deployment status.
>From here you can download or delete it.
<b>Active on this site:</b>
The MKP is installed, and the code distributed with it is currently active on this site.
<b>Enabled (inactive on this site):</b>
This is the bit that is new.
There are reasons why we may not be able to install an MKP: It might not be suitable for this Checkmk version, or collide with another package.
In this case, the MKP is marked as <i>"enabled"</i>, but it is not installed.
In a distributed setup this information is passed to the remote sites.
During a version upgrade or after a new configuration has been pushed to a remote site, every site re-evaluates all enabled (and active) MKPs.
The outdated ones are disabled, and all applicable ones are installed.
This way users can maintain MKPs for different Checkmk versions providing the same functionality.
ID: 14814
Title: Proxmox agent can handle rebooting VMs
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
In case of the reboot of a proxmox node the proxmox special agent crashed.
This has been fixed now.
Instead of crashing it now returns no data. This could lead to the service
going into an unkown state during the reboot.
ID: 14813
Title: EMC VNX Section fix
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The EMC VNX agent would sometimes begin an agent section with a leading space, " <<<" instead of "<<<".
This lead to a "ValueError" during discovery.
This has been fixed now. No user interaction required.