Werk 16414 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Migrate Old Configuration Format For 'Disable notifications'
Class: fix
Compatible: compat
Component: notifications
Date: 1710770356
Edition: cre
Level: 1
Version: 2.2.0p25
In Werk #6417, we announced that some changes to <code>etc/check_mk/conf.d/wato/contacts.mk</code> are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
C+:
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
C-:
With this Werk, the configuration is migrated automatically.
------------------------------------<diff>-------------------------------------------
- Title: Support Old Configuration Format For 'Disable notifications'
? ^^^^^
+ Title: Migrate Old Configuration Format For 'Disable notifications'
? ^^^ + +
Class: fix
Compatible: compat
Component: notifications
Date: 1710770356
Edition: cre
Level: 1
Version: 2.2.0p25
In Werk #6417, we announced that some changes to <code>etc/check_mk/conf.d/wato/contacts.mk</code> are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
C+:
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
C-:
- This crash is now no longer shown.
+ With this Werk, the configuration is migrated automatically.
Title: Support Old Configuration Format For 'Disable notifications'
Class: fix
Compatible: compat
Component: notifications
Date: 1710770356
Edition: cre
Level: 1
Version: 2.2.0p25
In Werk #6417, we announced that some changes to <code>etc/check_mk/conf.d/wato/contacts.mk</code> are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
C+:
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
C-:
This crash is now no longer shown.
[//]: # (werk v2)
# rmk: Remove 'Load environment variables from file' field in Robotmk Scheduler bakery rule
key | value
---------- | ---
date | 2024-03-27T14:51:09+00:00
version | 2.3.0b4
class | feature
edition | cee
component | wato
level | 1
compatible | no
Users who have configured the 'Load environment variable from file' field in the Robotmk Scheduler rule are affected by this incompatible werk. Any rules that contain the value for this field will be automatically migrated during the update and the value will be removed from the rules.
Originally, this field was designed to be fully compatible with Robots that could be used within Robocorp's cloud environment.
However, as Robocorp shifted its focus from Robot Framework to Python developers, the need for the VS Code extensions provided by Robocorp became redundant. The language server for Robot Framework would no longer be maintained, and the "RobotCode" extension would no longer serve Robot Framework users. In addition, both extensions had a rather confusing interface and didn't work well together. Now the RobotCode extension is the only necessary extension for VS Code, and it works very well.
The env.json file generated from this field was used exclusively by the Robocorp extension. This approach allowed local initiation and debugging of automations with the exact set of environment variables configured, mirroring those set later in the Cloud UI.
For the above reasons, we decided to remove this field.
[//]: # (werk v2)
# Make scp command work as site userr on SLES 15
key | value
---------- | ---
date | 2024-03-28T08:38:12+00:00
version | 2.4.0b1
class | fix
edition | cre
component | omd
level | 1
compatible | yes
On SUSE Linux Enterprise Server 15 systems, the `scp` command could crash with
```
/usr/bin/ssh: symbol lookup error: /usr/bin/ssh: undefined symbol: EVP_KDF_CTX_free, version OPENSSL_1_1_1d lost connection
```
when executed as a site user.
Title: Crash in agent bakery GUI after cloning a site
Class: fix
Compatible: compat
Component: agents
Date: 1711098828
Edition: cee
Level: 1
Version: 2.2.0p25
After cloning a site with <code>omd cp</code> or renaming it with <code>omd mv</code>, opening the agent bakery GUI
did result in a crash, showing a message like
C+:
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.
C-:
As a workaround, you can delete the file <code>~/var/check_mk/wato/bakery_file_status.mk</code>
on the site.
Title: mk_postgres: Ensure coherent string encoding
Class: fix
Compatible: compat
Component: checks
Date: 1711529016
Edition: cre
Level: 1
Version: 2.2.0p25
Postgres.cfg was always read as unicode decoded.
This ensures that the read text is correctly converted to byte string format.
Werk 16414 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Migrate Old Configuration Format For 'Disable notifications'
key | value
---------- | ---
date | 2024-03-18T13:59:16+00:00
version | 2.4.0b1
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
In Werk #6417, we announced that some changes to `etc/check_mk/conf.d/wato/contacts.mk` are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
```
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
```
With this Werk, the configuration is migrated automatically.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # Support Old Configuration Format For 'Disable notifications'
? ^^^^^
+ # Migrate Old Configuration Format For 'Disable notifications'
? ^^^ + +
key | value
---------- | ---
date | 2024-03-18T13:59:16+00:00
version | 2.4.0b1
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
In Werk #6417, we announced that some changes to `etc/check_mk/conf.d/wato/contacts.mk` are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
```
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
```
- This crash is now no longer shown.
+ With this Werk, the configuration is migrated automatically.
Werk 16409 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Prometheus & Alertmanager: Removal of 'IP Address' and 'Host name' options
key | value
---------- | ---
date | 2024-03-07T17:16:21+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
In Werk #14573, the deprecation of the options 'IP Address' and 'Host name' of the rules Prometheus
and Alertmanager was announced and described. This Werk removes these options.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Prometheus & Alertmanager: Removal of 'IP Address' and 'Host name' options
key | value
---------- | ---
date | 2024-03-07T17:16:21+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
- compatible | no
? ^^
+ compatible | yes
? ^^^
In Werk #14573, the deprecation of the options 'IP Address' and 'Host name' of the rules Prometheus
and Alertmanager was announced and described. This Werk removes these options.
[//]: # (werk v2)
# EC: Fix erroneous truncation of messages by the EC
key | value
---------- | ---
date | 2024-03-27T15:41:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | ec
level | 1
compatible | yes
Messages missing the end of line terminator were ignored by mkeventd in some cases.
This has been fixed.