[//]: # (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 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.3.0b4
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.3.0b4
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)
# Prometheus & Alertmanager: Removal of 'IP Address' and 'Host name' options
key | value
---------- | ---
date | 2024-03-07T17:16:21+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | no
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)
# mk_postgres: Ensure coherent string encoding
key | value
---------- | ---
date | 2024-03-27T08:43:36+00:00
version | 2.3.0b4
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)
# EC: Fix erroneous truncation of messages by the EC
key | value
---------- | ---
date | 2024-03-27T15:41:36+00:00
version | 2.3.0b4
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.
[//]: # (werk v2)
# notifications: Crash on config page when rule exists with missing permissions
key | value
---------- | ---
compatible | yes
version | 2.3.0b4
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.
[//]: # (werk v2)
# Crash in agent bakery GUI after cloning a site
key | value
---------- | ---
date | 2024-03-22T09:13:48+00:00
version | 2.3.0b4
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)
# The configuration is correctly loaded by RRD helper processes
key | value
---------- | ---
date | 2024-03-26T10:03:03+00:00
version | 2.3.0b4
class | fix
edition | cee
component | core
level | 2
compatible | yes
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)
# Fix network scan fail to run due to invalid user
key | value
---------- | ---
date | 2024-03-27T09:40:30+00:00
version | 2.3.0b4
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.