[2.4.0] Checkmk Werk 16667 adapted: discovery: fix writing of autochecks file for nodes of cluster and aggregation of service labels on clusters

Werk 16667 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # discovery: fix writing of autochecks file for nodes of cluster and aggregation of service labels on clusters key | value ---------- | --- date | 2024-04-25T12:29:22+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes For clustered services, the nodes' autocheck files would be written with the aggregated clustered service information. This is incorrect because individual nodes should have their own service information. This could cause the non-clustered services to be overridden when a clustered service being discovered. And discovering a non-clustered services could also override the clustered services. This is now fixed and the individual node information is written to the autochecks file. This means that when applying changes to clustered services, non-clustered services will no longer be affected and vice versa. As part of this effort, the aggregation for service labels on clusters has also been fixed. This means that instead of using the labels of the first node, the aggregated labels of all nodes are being used. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # discovery: fix writing of autochecks file for nodes + # discovery: fix writing of autochecks file for nodes of cluster and aggregation of service labels on clusters key | value ---------- | --- date | 2024-04-25T12:29:22+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes - For clustered services the nodes' autocheck files would be written + For clustered services, the nodes' autocheck files would be written with the ? + +++++++++ - with the aggregated clustered service information. + aggregated clustered service information. This is incorrect because individual + nodes should have their own service information. - Now, at least for the autodiscovery, this is fixed and the individual - node information is written. + This could cause the non-clustered services to be overridden when a clustered + service being discovered. And discovering a non-clustered services could also + override the clustered services. + This is now fixed and the individual node information is written to the + autochecks file. + This means that when applying changes to clustered services, non-clustered + services will no longer be affected and vice versa. + + As part of this effort, the aggregation for service labels on clusters has also + been fixed. This means that instead of using the labels of the first node, the + aggregated labels of all nodes are being used. +