Rudder

Logs are not very helpful either:

2024-01-30 13:52:03+0000 WARN  nodes.pending - Node '378740d3-c4a9-4474-8485-478e7e52db53' accepted, but couldn't find it's inventory
2024-01-30 13:52:03+0000 WARN  explain_compliance.378740d3-c4a9-4474-8485-478e7e52db53 - Can not get compliance for node with ID '378740d3-c4a9-4474-8485-478e7e52db53' because it has no configuration id initialised nor sent reports (node just added ?)
2024-01-30 13:52:03+0000 WARN  explain_compliance.378740d3-c4a9-4474-8485-478e7e52db53 - Can not get compliance for node with ID '378740d3-c4a9-4474-8485-478e7e52db53' because it has no configuration id initialised nor sent reports (node just added ?)
2024-01-30 13:52:03+0000 INFO  dynamic-group - Dynamic group all-nodes-with-cfengine-agent: added node with id: [ 378740d3-c4a9-4474-8485-478e7e52db53 ], removed: nothing
2024-01-30 13:52:03+0000 INFO  dynamic-group - Dynamic group hasPolicyServer-root: added node with id: [ 378740d3-c4a9-4474-8485-478e7e52db53 ], removed: nothing
2024-01-30 13:52:03+0000 INFO  policy.generation - Start policy generation, checking updated rules
2024-01-30 13:52:03+0000 INFO  policy.generation - [metrics] Xmx:1 GB nodes:3 (cached:2) rules:4 (enabled:4) techniques:10 (enabled:10) directives:10 (enabled:10) groups:2 (dynamic:2) parameters:2
2024-01-30 13:52:03+0000 ERROR policy.generation - Error when trying to get the CFEngine-MD5 digest for certificate of node 'node2.hostname.local' (378740d3-c4a9-4474-8485-478e7e52db53) <- CryptoEx: Key '-----BEGIN CERTIFICATE-----
MIIFqDCC[...]3tALNn
-----END CERTIFICATE-----' cannot be parsed as a valid certificate; root exception was: unable to decode base64 string: invalid characters encountered in base64 data
2024-01-30 13:52:03+0000 ERROR policy.generation - Error when trying to get the sha-256 digest of Certificate for node 'node2.hostname.local' (378740d3-c4a9-4474-8485-478e7e52db53): CryptoEx: Key '-----BEGIN CERTIFICATE-----
MIIFqDCC[...]3tALNn
-----END CERTIFICATE-----' cannot be parsed as a valid certificate; root exception was: unable to decode base64 string: invalid characters encountered in base64 data
2024-01-30 13:52:03+0000 INFO  policy.generation - Configuration of 2 nodes were updated, their policies are going to be written
2024-01-30 13:52:03+0000 INFO  scheduled.job - Update in node inventories main information detected: triggering a policy generation

(even if we ignore the part with the bad certificate)