Bug #15547
closed
Empty keyhashes in nodeslist.json on Linux nodes
Description
In Rudder 5.1, nodeslist.json key-hashes's fields are empty, and there's an error when "rudder agent inventory" is launched.
error log :
@[root@server sbin]# rudder agent inventory
Rudder agent 5.1.0.alpha1.git201908210250
Node uuid: root
error: Anomalous ending '
error: Anomalous ending '
error: Anomalous ending '
error: Anomalous ending '
error: Anomalous ending '
error: Anomalous ending '
error: Anomalous ending '
Start execution with config [20190821-143506-4976153c]
M| State Technique Component Key Message
E| compliant Inventory inventory The inventory has been successfully sent
info Rudder agent was run on a subset of policies - not all policies were checked
- Summary #####################################################################
1 components verified in 3 directives
=> 1 components in Enforce mode
-> 1 compliant
Execution time: 2.96s
################################################################################@
Updated by Nicolas CHARLES over 5 years ago
The node has a certificates, and so in policy generation we have
INFO com.normation.rudder.domain.nodes.NodeInfo - Node 'server.rudder.local' (root) is a Dsc node and a we do not know how to generate a hash yet
has it hasn't been implemented yet
Updated by Nicolas CHARLES over 5 years ago
- Status changed from New to In progress
- Assignee changed from Armand Sylvain to Nicolas CHARLES
Updated by Nicolas CHARLES over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2417
Updated by Nicolas CHARLES over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d3cc854f7e5d073e39140b2cc9b87218d44bc0a8.
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0~beta1 which was released today.