Title: agent_kube: requests.SSLError raised on connection using self signed certificates
Class: fix
Compatible: compat
Component: checks
Date: 1725278477
Edition: cre
Level: 1
Version: 2.2.0p33
Newer versions of `requests` don't take `REQUESTS_CA_BUNDLE` into account, resulting in
```
requests.exceptions.SSLError: \
HTTPSConnectionPool(host='<collector>', port=443): \
Max retries exceeded with url: \
/metadata (Caused by SSLError( \
SSLCertVerificationError(1, \
'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: \
self signed certificate in certificate chain (_ssl.c:1006)')))
```
being raised if running `agent_kube` against instances using self signed certificates.
This change invokes `session.merge_environment_settings()` to take `REQUESTS_CA_BUNDLE` into
account again.
See
[GitHub: 2807: Use merge_environment_settings method in sessions.send method](https://github.com/psf/requests/issues/2807)
and
[GitHub: 3626: HTTP Proxy with prepared request (honouring env. var.)](https://github.com/psf/requests/issues/3626)
Title: HTML Email: Handle SMTP return code 554 as permanent error
Class: fix
Compatible: compat
Component: notifications
Date: 1725281302
Edition: cre
Level: 1
Version: 2.2.0p33
If you used "Enable synchronous delivery via SMTP" the return code 554 was not
handled as a permanent error, leading to multiple delivery attempts.
This return code is now handled as permanent error.
Werk 16594 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Container: Support setting custom timezone
Class: feature
Compatible: compat
Component: packages
Date: 1724255060
Edition: cre
Level: 1
Version: 2.2.0p33
The checkmk containers now support setting the TZ variable for a container to specify what timezone the site should use.
The timezone information is then set for the site running inside the container.
This removes the need to mount timezone files from the host machine into a docker container.
A run command can look like this: `docker container run ... --env TZ="Europe/Berlin" check-mk-enterprise:<version>`
------------------------------------<diff>-------------------------------------------
Title: Container: Support setting custom timezone
Class: feature
Compatible: compat
Component: packages
Date: 1724255060
Edition: cre
Level: 1
Version: 2.2.0p33
The checkmk containers now support setting the TZ variable for a container to specify what timezone the site should use.
The timezone information is then set for the site running inside the container.
This removes the need to mount timezone files from the host machine into a docker container.
+ A run command can look like this: `docker container run ... --env TZ="Europe/Berlin" check-mk-enterprise:<version>`
+
[//]: # (werk v2)
# Use SHA256 digest when baking RPMs
key | value
---------- | ---
date | 2024-08-20T12:18:33+00:00
version | 2.3.0p15
class | feature
edition | cee
component | agents
level | 1
compatible | yes
The agent bakery now uses SHA256 for digests in the package header when creating RPM packages.
Specifically, this means `rpmbuild` is now invoked with the macros
```
%_source_filedigest_algorithm 8
%_binary_filedigest_algorithm 8
```
where `8` signifies SHA256. See `man rpmsign` for further information.
[//]: # (werk v2)
# HTML Email: Handle SMTP return code 554 as permanent error
key | value
---------- | ---
compatible | yes
version | 2.3.0p15
date | 2024-09-02T12:48:22+00:00
level | 1
class | fix
component | notifications
edition | cre
If you used "Enable synchronous delivery via SMTP" the return code 554 was not
handled as a permanent error, leading to multiple delivery attempts.
This return code is now handled as permanent error.
Werk 16594 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Container: Support setting custom timezone
key | value
---------- | ---
date | 2024-08-21T15:44:20+00:00
version | 2.3.0p14
class | feature
edition | cre
component | packages
level | 1
compatible | yes
The checkmk containers now support setting the TZ variable for a container to specify what timezone the site should use.
The timezone information is then set for the site running inside the container.
This removes the need to mount timezone files from the host machine into a docker container.
A run command can look like this: `docker container run ... --env TZ="Europe/Berlin" check-mk-enterprise:<version>`
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Container: Support setting custom timezone
key | value
---------- | ---
date | 2024-08-21T15:44:20+00:00
version | 2.3.0p14
class | feature
edition | cre
component | packages
level | 1
compatible | yes
The checkmk containers now support setting the TZ variable for a container to specify what timezone the site should use.
The timezone information is then set for the site running inside the container.
This removes the need to mount timezone files from the host machine into a docker container.
+ A run command can look like this: `docker container run ... --env TZ="Europe/Berlin" check-mk-enterprise:<version>`
Werk 16997 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# NagVis: Updated to 1.9.43
key | value
---------- | ---
date | 2024-08-30T07:45:48+00:00
version | 2.4.0b1
class | fix
edition | cre
component | packages
level | 1
compatible | yes
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# NagVis: Updated to 1.9.43
key | value
---------- | ---
date | 2024-08-30T07:45:48+00:00
- version | 2.3.0p14
? ^ ^ -
+ version | 2.4.0b1
? ^ ^
class | fix
edition | cre
component | packages
level | 1
compatible | yes