[Release] Checkmk stable release 2.2.0p22

Announcements
, , ,
1

Dear friends of Checkmk,

the new stable release 2.2.0p22 of Checkmk is ready for download.

This stable release ships with 23 changes affecting all editions of Checkmk,
4 changes for the Enterprise editions, 0 Cloud Edition specific and
0 Managed Services Edition specific changes.

Changes in all Checkmk Editions:

BI

  • 14222 BI configuration: Changed element order of “restrict severity to at worst”…

Checks & agents

  • 16490 NetApp: new addition of datasource program and check plugins for NetApp ONTAP…
  • 16333 FIX: if_lancom: Switch port discovery does not work for Lancom routers when the router description is configured to be used for the Service Description…
    NOTE: Please refer to the migration notes!
  • 16325 FIX: netapp_ontap_psu: fix discovery ruleset…
    NOTE: Please refer to the migration notes!
  • 15322 FIX: BGP Peer State Mapping: add connect state…
  • 16376 FIX: DCD: Not respecting “Validity of missing data” setting…
  • 15324 FIX: agent_bakery: mk_postgres.py: restore required keys…
  • 16402 FIX: azure_vm_network_io: KeyError (total_Network_In_Total)…
  • 16336 FIX: lnx_video: Fix section parsing…
  • 15976 FIX: mssql_backup: Correct timezone difference for last backup date…
  • 16327 FIX: netapp_ontap_environment: show unit of measurement in summary…
  • 16489 FIX: netapp_ontap_vs_traffic: add missing svm_nfs_v3 counters…

REST API

  • 16364 FIX: tag_group: change the identification field from ‘ident’ to ‘id’…
    NOTE: Please refer to the migration notes!
  • 16390 FIX: notification_rule: cancel previous notifications now working with custom plugin scripts…
  • 16387 FIX: notification_rules: custom plugins now created correctly when using the REST-API…
  • 16366 FIX: rule: Fix crash on rule creation via REST API without conditions or properties…
  • 16465 FIX: service discovery: introduce functionality to fetch job status from remote sites…

Setup

  • 16389 FIX: authentication: remove user profile dir when unknown user and failed to login…

Site management

  • 16401 FIX: omd start mkeventd: Error Code of Event Daemon…

User interface

  • 16470 FIX: Fix topics being falsely shown as public…
    NOTE: Please refer to the migration notes!
  • 16471 FIX: Hide private topics in dropdowns…
  • 16315 FIX: Respect sort index for listed dashboards in page menu…
  • 16473 FIX: Support host & service labels in CSV exports again…

Changes in the Checkmk Enterprise Edition:

Agent bakery

  • 16083 FIX: mk_inventory: Regression in bakery plugin…

Livestatus proxy

  • 16448 FIX: Fix inventory sync of hosts if remote data is updated at the time when liveproxyd sync starts or ends…
  • 16447 FIX: Fix inventory sync of subsequent hosts if a previous one has invalid data

Setup

  • 16365 FIX: baked_agents: Fix version displayed on agent files…

Changes in the Checkmk Cloud Edition:

NO CHANGES

Changes in the Checkmk Managed Services Edition:

NO CHANGES

You can download Checkmk from our download page: Download Checkmk for free | Checkmk

List of all changes: Werks

We greatly thank you for using Checkmk and wish you a successful monitoring,

Your Checkmk Team

3 Likes
2

Hi all,

we have an issue with the Service Discovery Endpoint (/service_discovery_run/actions/start/invoke) in Distributed Monitoring after upgrading to version 2.2.0p22.

This might be related to the Werk service discovery: introduce functionality to fetch job status from remote sites.

After adding the Host via the Rest API, we are excecuting the service discovery and activate the changes via the API.

This still works when the host is on the central site, but when the host is on a remote site we got the an HTTP Code 500 from the Service Discovery with the following error: MKUserError(None, "Host could not be found.", status=404)

When we activate the changes and doing the service discovery again it works, but that is only a workaround.

Is this a bug, can someone reproduce this?

Best Regards
Thomas

3

HI Thomas.

Thanks for reporting it.
Could you please share the REST API endpoint used by you and also the exact steps performed after you add the host on the remote site?

4

Hi,

we add the host with the “Create a host” Endpoint and the following payload:

{
“folder”: “/server/unix/linux”,
“host_name”: “myhost.local”,
“attributes”: {
“site”: “dev_remote1”,
“alias”: “ansible_installed” }
}

After that (without activation) we run the “Execute a service discovery on a host” Endpoint (/api/1.0/domain-types/service_discovery_run/actions/start/invoke) with the following Payload and got the error that the host is not found:

{
“host_name”: “myhost.local”,
“mode”: “refresh”
}

The host is visible in the UI (central site) and it is the same Ansible Role which we used before the upgrade.

Our checkmk Dev environment is a distributed environment with a central site and 3 remote sites, configuration synchronisation is enabled.
The API Calls are run against the central site.

All sites are upgraded to version 2.2.0p22 (Enterprise Edition).

Let me know when you need more informations.

5

Morning,
we were able to reproduce this issue in another environment. So, it seems to me, that this is a bug?

regards
Christian

6

Thanks for the repro.
We have opened an internal ticket on this problem.
Will update you ASAP.

2 Likes
7

Its fixed as part of this werk service_discovery: allow discovery on fresh remote host

3 Likes