[//]: # (werk v2)
# Support host & service labels in CSV exports again
key | value
---------- | ---
date | 2024-02-08T17:25:53+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
In [Werk #13729](https://checkmk.com/werk/13729) support for labels in CSV
exports was removed (among other things). Instead, for affected columns a
constant `"NOT_CSV_EXPORTABLE"` value was exported.
This change reintroduces host & service labels as JSON serialized strings. This
only relates to CSV exports, other formats are not affected.
Sample export:
```csv
"host";"host_labels"
"test";"{""cmk\/os_platform"": ""linux"", ""cmk\/os_family"": ""linux"", ""cmk\/check_mk_server"": ""yes"", ""cmk\/site"": ""test""}"
"dummy";"{""my_label"": ""works""}"
"nothing";"{}"
```
[//]: # (werk v2)
# ldap_connection: When you create/clone a new ldap connection, the ID will now be unique
key | value
---------- | ---
date | 2024-02-09T15:54:09+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Previously, when creating a new LDAP connection via the UI, you could provide
an ID that was already in use by another user connection. This is no longer
the case with this werk. Now, when you clone a connection, a new unique ID
will be generated from the cloned connection. If you create a new connection,
the ID must be unique or you will get an error.
Title: mk_inventory: Regression in bakery plugin
Class: fix
Compatible: compat
Component: agents
Date: 1707400951
Edition: cee
Knowledge: doc
Level: 1
Version: 2.2.0p22
This werk fixes a regression that came up with Checkmk 2.2.0,
only affecting windows agents.
While patching the `mk_inventory.vbs` script, the agent bakery
accidentally specified `exe_paths` two times, instead of once
`exePaths` and once `regPaths`.
Title: lnx_video: Fix section parsing
Class: fix
Compatible: compat
Component: checks
Date: 1707412972
Edition: cre
Level: 1
Version: 2.1.0p40
The output of the 'lspci' command was not consistent. This caused the parsing of the lnx_video section to fail.
As a consequnce, the graphics cards were not shown in the HW/SW inventory.
This has now been fixed and the graphics cards will be shown.
Title: Fix inventory sync of subsequent hosts if a previous one has invalid data
Class: fix
Compatible: compat
Component: liveproxy
Date: 1707132754
Edition: cee
Level: 1
Version: 2.2.0p22
Title: Fix inventory sync of hosts if remote data is updated at the time when liveproxyd sync starts or ends
Class: fix
Compatible: compat
Component: liveproxy
Date: 1707132975
Edition: cee
Level: 1
Version: 2.2.0p22
When the liveproxyd starts or ends at a particular time TS and remote inventory
data is written between TS and \<TS+1 then it's not synced.
Title: rule: Fix crash on rule creation via REST API without conditions or properties
Class: fix
Compatible: compat
Component: rest-api
Date: 1707462364
Edition: cre
Level: 1
Version: 2.2.0p22
Before this Werk, an status code 500 Internal Server Error was returned when creating a
rule without conditions or properties. This Werk fixes it and now it is possible to create
a rule in such conditions.
Title: lnx_video: Fix section parsing
Class: fix
Compatible: compat
Component: checks
Date: 1707412972
Edition: cre
Level: 1
Version: 2.2.0p22
The output of the 'lspci' command was not consistent. This caused the parsing of the lnx_video section to fail.
As a consequnce, the graphics cards were not shown in the HW/SW inventory.
This has now been fixed and the graphics cards will be shown.
[//]: # (werk v2)
# Fix inventory sync of subsequent hosts if a previous one has invalid data
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-02-05T11:32:34+00:00
level | 1
class | fix
component | liveproxy
edition | cee
[//]: # (werk v2)
# Fix inventory sync of hosts if remote data is updated at the time when liveproxyd sync starts or ends
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-02-05T11:36:15+00:00
level | 1
class | fix
component | liveproxy
edition | cee
When the liveproxyd starts or ends at a particular time TS and remote inventory
data is written between TS and \<TS+1 then it's not synced.