[Release] Checkmk stable release 2.1.0p18

Announcements
, , , ,
1

Dear friends of Checkmk,

the new stable release 2.1.0p18 of Checkmk is ready for download.

This maintenance release ships with 29 changes affecting all editions of Checkmk,
2 Enterprise Edition specific changes and 0 Managed Services Edition specific changes.

Support periods can be found here: Checkmk versions

Changes in all Checkmk Editions:

Agent bakery:

  • 15033 FIX: check_mk_agent.linux: increase refresh interval for chrony section…
  • 14706 FIX: mrpe: Fix missing output in agents if async execution enabled…
  • 14703 FIX: sap_hana: Fix agent plugin crash when querying fileinfo…

BI:

  • 15013 FIX: $HOSTADDRESS and $HOSTNAME can now be used in aggregation names

Checks & agents:

  • 14989 FIX: Extension package: Disable right MKP after a version was changed
  • 14986 FIX: FileNotFoundError in update-pre-hooks script “01_mkp-disable-outdated”…
  • 14705 FIX: fileinfo_groups: Fix state for ‘Out of relevant time of day’…
  • 14704 FIX: mk_mysql: Support for multiple sockets and aliases…
  • 14975 FIX: mk_postgres.py: correct UNIX socket not found when instances are configured…
  • 14702 FIX: ps: Fix crash if user or cgroup are empty…
  • 15035 FIX: wut_webio: handling of case when state is empty
  • 14827 FIX: mk_sshd_config: Monitor effective SSH daemon configuration…
    NOTE: Please refer to the migration notes!

Configuration generation:

  • 14701 FIX: automatic discovery: Fix automatic configuration update…

Livestatus:

  • 14687 FIX: Fixed JSON encoding outside the BMP for Livestatus…

Metrics system:

  • 14780 FIX: Remove thresholds to new carbon/influxdb/RRD metrics…
    NOTE: Please refer to the migration notes!

Notifications:

  • 15004 FIX: Improved notification processing performance…

REST API:

  • 13967 FIX: “Topic” attribute for host tags is now optional in REST API…
  • 13969 FIX: ETag for root folder is not correctly generated
  • 14905 FIX: REST API: Allow single item lists for the sites parameter on the host/service status endpoints
  • 13970 FIX: Showing the config of an agent will no longer fail with a Permission Mismatch

Setup:

  • 14779 Remove less useful graphs…
  • 14924 SEC: Fix CSRF in add-visual endpoint…
  • 14985 FIX: Broken agent downloads: “This host has no Checkmk agents”
  • 15002 FIX: Fix “Base on role” default while cloning roles…
  • 15001 FIX: Fix possibility that changes made by form dialogs were not persisted…

Site management:

  • 15040 FIX: Make curl command work as site user on SLES 15 SP4…

User interface:

  • 15038 FIX: Distributed configuration: Fix active Setup menu on remote site…
  • 15005 FIX: Fix possible KeyError on service graphs view
  • 15003 FIX: Fix wrong results in view on combined host tag search

Changes in the Checkmk Enterprise Edition:

Agent bakery:

  • 13441 FIX: Baking agent with encrypted realtime checks

Reporting & availability:

  • 15000 FIX: Fix combined graphs in reports…

Changes in the Checkmk Managed Services Edition:

You can download Checkmk from our download page:

Please mail bug reports and qualified feedback to feedback@checkmk.com.
We greatly thank you for using Checkmk and wish you a successful monitoring,

Your Checkmk Team

3 Likes
2

Sorry but where do I find the mentioned “Migration Notes”?

Cheers

3

I think it’s supposed to be these werks? There are some notes on what’s changing or what needs to be done if manual interaction is needed.

Werk #14780
Werk #14827

4

Thanks! I guess it would help to include these links in the release notes?

1 Like
5

@tboston if you go to https://checkmk.com/werk/<insert_werk_number> you get there.

1 Like
6

Still, I think it would help to add this hint to the Release Announcements anyway. :slight_smile:

2 Likes
7

Also, you can find the information within your site, on the lower left:
image
Those are the incompatible Werks. If you are told to look for the “Migration notes”, that is the place to be.

1 Like
8

I think @Sara is actually looking into that, so let me put her on the spot here. :yum:

3 Likes
9

But then its too late because I already updated, correct?

1 Like
10

exactly! :wink: But most likly you will have a test site for that :wink:

2 Likes
11

Hello!
@robin.gierse is correct, I’ve looked into that with the dev team :slight_smile:
They actually have this improvement in their backlog, but unfortunately I am not sure when we could expect it to be implemented.

It is a nice thing to have – we might just need to wait a bit.

2 Likes
12

Well, I feel that we’re not on the same page here. I just asked if you can add the hint on how to get to the migration notes/werks in such Release Posts here in the forum. Nothing more.

Regarding the test site, sure, unless monitoring is not your only topic and you have a big IT-Team. I wouldn’t say that having a test site is a regular ‘thing’, though maybe thats just me. We do not have a test-site and we’d like to check everything before we update.

2 Likes
13

Hey @tboston,
If you want to see a list of werks for a specific version you can always get them like this:
https://checkmk.com/werks?product=cmk&version=2.1.0p19

So you can simply add/change the query parameter to the version you are interested in.

2 Likes
14

Check out the latest release post. It includes links to the werks.

3 Likes
15

I know its an extra mile for every release post - but worth it! much appreciated