[//]: # (werk v2)
# mk_postgres: Ensure coherent string encoding
key | value
---------- | ---
date | 2024-03-27T08:43:36+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Postgres.cfg was always read as unicode decoded.
This ensures that the read text is correctly converted to byte string format.
[//]: # (werk v2)
# notifications: Crash on config page when rule exists with missing permissions
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-03-27T09:39:50+00:00
level | 1
class | fix
component | notifications
edition | cre
When a user tries to access the notification setup page where
a rule is listed for which the user does not have access rights,
the page would crash making any changes impossible.
With this werk, the table generation is fixed and the page will
no longer crash the GUI.
Title: The configuration is correctly loaded by RRD helper processes
Class: fix
Compatible: compat
Component: core
Date: 1711447383
Edition: cee
Level: 2
Version: 2.1.0p42
This change ensures the reloading of the configuration by already
running RRD processes, thereby guaranteeing that those processes are
using the correct configuration.
SUP-17787
CMK-16318
Title: Changing settings in the site configuration can no longer cause ActivateChanges to hang forever
Class: fix
Compatible: compat
Component: wato
Date: 1711528118
Edition: cre
Level: 1
Version: 2.1.0p42
Title: notifications: Crash on config page when rule exists with missing permissions
Class: fix
Compatible: compat
Component: notifications
Date: 1711532390
Edition: cre
Level: 1
Version: 2.2.0p25
When a user tries to access the notification setup page where
a rule is listed for which the user does not have access rights,
the page would crash making any changes impossible.
With this werk, the table generation is fixed and the page will
no longer crash the GUI.
Title: The configuration is correctly loaded by RRD helper processes
Class: fix
Compatible: compat
Component: core
Date: 1711447383
Edition: cee
Level: 2
Version: 2.2.0p25
This change ensures the reloading of the configuration by already
running RRD processes, thereby guaranteeing that those processes are
using the correct configuration.
SUP-17787
CMK-16318
[//]: # (werk v2)
# Crash in agent bakery GUI after cloning a site
key | value
---------- | ---
date | 2024-03-22T09:13:48+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
After cloning a site with `omd cp` or renaming it with `omd mv`, opening the agent bakery GUI
did result in a crash, showing a message like
```
Internal error: '/omd/sites/SITE/share/check_mk/agents/check_mk_agent.linux' is not in the subpath of '/omd/sites/SITE_COPY/share/check_mk/agents' OR one path is relative and the other is absolute.
```
As a workaround, you can delete the file `~/var/check_mk/wato/bakery_file_status.mk`
on the site.
[//]: # (werk v2)
# Rename service labels for Robotmk
key | value
---------- | ---
date | 2024-03-25T12:28:56+00:00
version | 2.3.0b4
class | feature
edition | cee
component | multisite
level | 2
compatible | yes
This is a follow-up for werk #13872.
The service labels have been renamed to 'cmk/rmk/html_last_log:yes' and 'cmk/rmk/html_last_error_log:yes'.
The icons for the last log file and last error log file will have an icon based on the new labels as well as the old ones from werk #13872.
[//]: # (werk v2)
# Fix network scan fail to run due to invalid user
key | value
---------- | ---
date | 2024-03-27T09:40:30+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Before this Werk, when running the scheduled network scan for a folder
it failed with the message "An exception occured: Invalid username:
'Network scan'". This Werk fixes that problem and now the network scan
runs correctly with the configured user.
[//]: # (werk v2)
# rmk: Ignore RCC suites and RCC profile configuration if CORE mode is active
key | value
---------- | ---
date | 2024-03-21T15:36:04+00:00
version | 2.3.0b4
class | fix
edition | cee
component | checks
level | 1
compatible | yes
When the Robotmk Core MKP is installed, RCC Suites configuration and RCC Profile configuration are not available as they are Enterprise features.
Previously, there were scenarios where RCC suites were running even though the Robotmk Core MKP was installed.
The Agent Bakery would use previously saved Enterprise configurations without first migrating them to their CoreMode counterparts.
This has now been fixed and the licensing mode is checked when the agent is baked. This means the RCC Suites/RCC Profile configuration will be ignored during the bake process.
This prevents users from inadvertently relying on a paid feature when CoreMode is enabled.