Werk 16025 was deleted. The following Werk is no longer relevant.
Title: Update PHP version in SLES15SP3 from 7 to 8
Class: fix
Compatible: incomp
Component: rpm
Date: 1701254497
Edition: cre
Level: 2
Version: 2.2.0p17
Checkmk was shipped with a dependency to PHP7 for SLES15SP3. Since PHP7 is
part of the legacy module, this Werk updates the dependency from PHP7 to PHP8.
As SLES only allows one version of PHP to be installed, the following steps
will uninstall PHP7 from the system and install the new version of Checkmk
with PHP8. Be aware that this procedure updates PHP from version 7 to 8 for the whole OS. In case you run additional PHP applications next to Checkmk, the update will also affect them.
Run the following commands to perform the update to the new Checkmk version:
* add SLES-15SP4 repo to get PHP8 with <tt>zypper addrepo https://updates.suse.com/SUSE/Products/SLE-BCI/15-SP4/x86_64/product/ sles15sp4</tt>
* install the new Checkmk version with <tt>zypper install NEW_CHECKMK.rpm</tt>
* Zypper will now complain about a conflict with several PHP packages and asks you to select a solution. There, select <tt>solution 1</tt> to confirm the deinstallation of the current Checkmk version, the PHP7 modules and to continue with the installation
* confirm the installation of the new Checkmk version and PHP8 with <tt>yes</tt>
* removing the existing Checkmk version will throw an error like `Site <SITENAME> is still using this version! Removal of <OLD_CHECKMK>(@System) failed:`, proceed by choosing <tt>ignore</tt> which creates a inconsistent state for the old Checkmk version package, which we will resolve in a later step.
* PHP7 will be removed and PHP8 gets installed
* change to the site user with <tt>omd su SITE_NAME</tt>
* stop the site with <tt>omd stop</tt>
* perform the update to the new Checkmk version with <tt>omd update</tt>, select <tt>Update</tt> at the user prompt
* in case further prompts regarding wrong permissions of BUILD files appear, choose the default value with <tt>d</tt>
* start the site again with <tt>omd start</tt>
* exit from the site user
* list all installed Checkmk version with <tt>omd versions</tt>
* finally remove the old Checkmk installation with <tt>zypper remove OLD_CHECKMK</tt>
Werk 16025 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Update PHP version in SLES15SP3 from 7 to 8
Class: fix
Compatible: incomp
Component: rpm
Date: 1701254497
Edition: cre
Level: 2
Version: 2.2.0p17
Checkmk was shipped with a dependency to PHP7 for SLES15SP3. Since PHP7 is
part of the legacy module, this Werk updates the dependency from PHP7 to PHP8.
As SLES only allows one version of PHP to be installed, the following steps
will uninstall PHP7 from the system and install the new version of Checkmk
with PHP8. Be aware that this procedure updates PHP from version 7 to 8 for the whole OS. In case you run additional PHP applications next to Checkmk, the update will also affect them.
Run the following commands to perform the update to the new Checkmk version:
* add SLES-15SP4 repo to get PHP8 with <tt>zypper addrepo https://updates.suse.com/SUSE/Products/SLE-BCI/15-SP4/x86_64/product/ sles15sp4</tt>
* install the new Checkmk version with <tt>zypper install NEW_CHECKMK.rpm</tt>
* Zypper will now complain about a conflict with several PHP packages and asks you to select a solution. There, select <tt>solution 1</tt> to confirm the deinstallation of the current Checkmk version, the PHP7 modules and to continue with the installation
* confirm the installation of the new Checkmk version and PHP8 with <tt>yes</tt>
* removing the existing Checkmk version will throw an error like `Site <SITENAME> is still using this version! Removal of <OLD_CHECKMK>(@System) failed:`, proceed by choosing <tt>ignore</tt> which creates a inconsistent state for the old Checkmk version package, which we will resolve in a later step.
* PHP7 will be removed and PHP8 gets installed
* change to the site user with <tt>omd su SITE_NAME</tt>
* stop the site with <tt>omd stop</tt>
* perform the update to the new Checkmk version with <tt>omd update</tt>, select <tt>Update</tt> at the user prompt
* in case further prompts regarding wrong permissions of BUILD files appear, choose the default value with <tt>d</tt>
* start the site again with <tt>omd start</tt>
* exit from the site user
* list all installed Checkmk version with <tt>omd versions</tt>
* finally remove the old Checkmk installation with <tt>zypper remove OLD_CHECKMK</tt>
------------------------------------<diff>-------------------------------------------
Title: Update PHP version in SLES15SP3 from 7 to 8
Class: fix
Compatible: incomp
Component: rpm
Date: 1701254497
Edition: cre
Level: 2
- Version: 2.2.0p19
? ^
+ Version: 2.2.0p17
? ^
Checkmk was shipped with a dependency to PHP7 for SLES15SP3. Since PHP7 is
part of the legacy module, this Werk updates the dependency from PHP7 to PHP8.
As SLES only allows one version of PHP to be installed, the following steps
will uninstall PHP7 from the system and install the new version of Checkmk
with PHP8. Be aware that this procedure updates PHP from version 7 to 8 for the whole OS. In case you run additional PHP applications next to Checkmk, the update will also affect them.
Run the following commands to perform the update to the new Checkmk version:
* add SLES-15SP4 repo to get PHP8 with <tt>zypper addrepo https://updates.suse.com/SUSE/Products/SLE-BCI/15-SP4/x86_64/product/ sles15sp4</tt>
* install the new Checkmk version with <tt>zypper install NEW_CHECKMK.rpm</tt>
* Zypper will now complain about a conflict with several PHP packages and asks you to select a solution. There, select <tt>solution 1</tt> to confirm the deinstallation of the current Checkmk version, the PHP7 modules and to continue with the installation
* confirm the installation of the new Checkmk version and PHP8 with <tt>yes</tt>
* removing the existing Checkmk version will throw an error like `Site <SITENAME> is still using this version! Removal of <OLD_CHECKMK>(@System) failed:`, proceed by choosing <tt>ignore</tt> which creates a inconsistent state for the old Checkmk version package, which we will resolve in a later step.
* PHP7 will be removed and PHP8 gets installed
* change to the site user with <tt>omd su SITE_NAME</tt>
* stop the site with <tt>omd stop</tt>
* perform the update to the new Checkmk version with <tt>omd update</tt>, select <tt>Update</tt> at the user prompt
* in case further prompts regarding wrong permissions of BUILD files appear, choose the default value with <tt>d</tt>
* start the site again with <tt>omd start</tt>
* exit from the site user
* list all installed Checkmk version with <tt>omd versions</tt>
* finally remove the old Checkmk installation with <tt>zypper remove OLD_CHECKMK</tt>
Title: Event Console: Fix The EC always activates the config written by the previous activation.
Class: fix
Compatible: compat
Component: ec
Date: 1705414424
Edition: cre
Level: 2
Version: 2.2.0p19
The bug was introduced by the werk: [#16012](https://checkmk.com/werk/16012) in version 2.2.0p18.
A workaround would be: make a trivial change to the rules/rule packs (edit description)
and activate the changes. Or reload the EC manually after the initial reload to apply the correct config.
Title: ucd_disk: fs_size, fs_used and fs_free have wrongly scaled values in performance graphs
Class: fix
Compatible: compat
Component: checks
Date: 1705324957
Edition: cre
Level: 1
Version: 2.2.0p19
For <code>ucd_disk</code> a performance value translation had been missing, fixed by this change.
Title: mk_tsm: Fix export: =: is not an identifier
Class: fix
Compatible: compat
Component: checks
Date: 1705329209
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p19
Since Werk 16273 `eval` is no longer used to create the required environment.
In some setups, the following error occurs.
```
export: =: is not an identifier
```
With this Werk the error is fixed.
The error occured, if the ouput of `get_dsmserv_processes` consisted of a single linebreak.
[//]: # (werk v2)
# user_config: add verification for contact groups and locked attributes
key | value
---------- | ---
date | 2024-01-16T14:42:21+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
This werk introduces two changes:
* it now verifies for create & edit if the provided contact groups actually exist
* it verifies that for an edit request, locked attributes are not being modified
[//]: # (werk v2)
# user_config: verify contact group existence when creating or editing user
key | value
---------- | ---
date | 2024-01-11T13:32:35+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
[//]: # (werk v2)
# revert_changes: internal changes can be reverted only if the user has the correct permission
key | value
---------- | ---
date | 2024-01-17T11:41:59+00:00
version | 2.3.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Changes made by the checkmk internal user can now only be reverted when the
logged-in user has the permission "Discard foreign changes".
[//]: # (werk v2)
# Support Diagnostics: Also add the latest Crash Dumps to the SD Dump
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2023-09-27T16:54:11+00:00
level | 1
class | feature
component | setup
edition | cre
For each category of crash dumps (base, check, ec, gui, rest_api, section), add the latest dump
to the Support Diagnostics dump.
[//]: # (werk v2)
# Fix missing event console rules after site update
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-17T09:18:22+00:00
level | 1
class | fix
component | ec
edition | cee
With werk 16012 the event console rules are filtered ond saved to the location
var/mkeventd/active_config during activate changes.
This werk fixes the missing procedure while updating to a new Checkmk version.