CheckMK upgrade path

General
, ,
1

Hey guys,

Sorry for this very little topic but I want a strong confirmation before proceeding with, we are in 2.1 p42 and we want to upgrade to 2.3 latest.

  1. First 2.2 p01 on each nodes
  2. Latest 2.2 pxx on each nodes
  3. First 2.3 on each nodes
  4. latest 2.3 pxx on each nodes

I read this documentation Updates and Upgrades (checkmk.com) but couldn’t spot any info about it except 2.2 p8 but because we will upgrade to 2.2 latest before jumping to 2.3 it shouldn’t be a problem.

Any advice/remark regarding this path ?

Regards,

Vincent

CheckMK upgrade 2.1.0p15 -> 2.3.0p27 - Failed to parse graph update response: ERROR: None
2

Skip point 1 and 3.
Yesterday i upgraded a bigger system from 2.0.0pxx to actual 2.3 and it was working without problem to use every time the latest version of the major releases.

2 Likes
3

You are a lucky guy

regards

Mike

4

I wanted the check how the upgrade would take and 2.2 isn’t available for Debian 12 until p7, is that an issue ?

5

For people looking for an answer:

I was 2.1.0p42, so best is to upgrade to latest 2.1.0pxx, then latest 2.2.0pxxx and finally latest 2.3.0pxx

6

This isnt necessary, you can go from any 2.1.0pxx direct to any 2.2.0pxx

regards

Michael

7

The recommendation is to alway install the latest of the current version first. So the mentioned upgrade path is correct.

8

May you please share the reference.

This would cause a huge additional workload for us.
E.g. we are running 2.1.0p42 and plan to upgrade to 2.2.0 we first need to upgrade 300 remote sites to 2.1.0p45 and finally master to 2.1.0p45 before we can upgrade to 2.2.0pxx.
The upgrade needs a lot of planning and coordination and last ~ 2-3 month. Meanwhile 2.1.0p47 was released and we need to start the process from beginning. :frowning:

Since 1.4.0 we dont care about the latest patch level and do direct update to next version with highest patch level. If there is no urgent need we do not upgrade the patch level. In the past we had this only once in a smaller environment.

regards

Michael

9

The latest version i think is only relevant if your starting version is very old.
Something like you have a 2.1.0p9 running and want now to upgrade to 2.2
Here i would also recommend to first upgrade to a newer 2.1 version.
In your case with 2.1.0p42 i would also upgrade directly to 2.2.

1 Like
10

This is a recommendation, not a requirement, but there are some examples in the past, where this made sense and things easier.
But you are right, I would also not update sites from the second last to the last release.
It all depends on the bug fixes/ werks that have been released in the meantime and its up to you to test and verify the procedure.

1 Like
11

Good to know, still running on 2.1.0p5.
Hopefully workload allows me to update in some unknown future. :laughing:

1 Like
12

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.