Actions
Bug #12115
closedError "CFEngine-MD5 digest of CFEngine public key for node 'server.rudder.local'" on fresh install
Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
No
Description
On a fresh install, we get in the log (depending on some timing between things):
[2018-02-13 12:13:27] ERROR com.normation.rudder.domain.nodes.NodeInfo - Error when trying to get the CFEngine-MD5 digest of CFEngine public key for node 'server.rudder.local' (root) <- unable to decode base64 string: invalid characters encountered in base64 data [2018-02-13 12:13:27] ERROR com.normation.rudder.domain.nodes.NodeInfo - Error when trying to get the sha-256 digest of CFEngine public key for node 'server.rudder.local' (root) <- unable to decode base64 string: invalid characters encountered in base64 data
This message is not grave at all: it is due to the fact that we are initializing root server inventory with dummy data and that in that case, we didn't had received its real inventory. So we try to read a cfengine key from somthing that is not a cfengine key.
I'm opening that ticket to let other people know that it is not a problem for root server, just in the windows timelapse before the root server inventory is sent & processed.
We should avoid that message in that case (don't try to use that dummy key for ex).
We will need to have a correct solution for that for all nodes when implementing #7876
Actions