Actions
Enhancement #24105
closedEnhancement #24091: Add manufacturer field in create node API
Machine is not correctly create with node create API
Effort required:
Name check:
To do
Fix check:
Checked
Regression:
No
Description
See parentt ticket comments for details.
Updated by François ARMAND 10 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 10 months ago
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)
Updated by François ARMAND 10 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/5367
Updated by Anonymous 10 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|cd8c0bce6182a483ef659e6207de569288f0bf1d.
Updated by François ARMAND 10 months ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 10 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.11 which was released today.
Actions