Project

General

Profile

Actions

Bug #14304

closed

Dual inventory processing in logs

Added by Nicolas CHARLES almost 6 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System integration
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
32
Name check:
Fix check:
Regression:

Description

With Rudder Nightly 5.0.7-SNAPSHOT, on a Centos 7.4, i get a double log of inventory processing

[2019-02-13 08:57:01] DEBUG inventory-processing - watcher ignored file .davfs.tmp1b6bc9 (unrecognized extension: 'tmp1b6bc9')
[2019-02-13 08:57:01] DEBUG inventory-processing - watcher ignored file .davfs.tmp1b6bc9 (unrecognized extension: 'tmp1b6bc9')
[2019-02-13 08:57:01] DEBUG inventory-processing - watcher ignored file .davfs.tmp11ae79 (unrecognized extension: 'tmp11ae79')
[2019-02-13 08:57:01] DEBUG inventory-processing - watcher ignored file .davfs.tmp11ae79 (unrecognized extension: 'tmp11ae79')
[2019-02-13 08:57:01] INFO  inventory-processing - Watch new inventory file 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs' with signature available: process.
[2019-02-13 08:57:01] DEBUG inventory-processing - Start parsing inventory 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs'
[2019-02-13 08:57:01] INFO  inventory-processing - Watch new inventory file 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs' with signature available: process.
[2019-02-13 08:57:01] DEBUG inventory-processing - Start parsing inventory 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs'
[2019-02-13 08:57:01] DEBUG inventory-processing - Inventory 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs' parsed in 0 milliseconds ms, now saving
[2019-02-13 08:57:01] DEBUG inventory-processing - Inventory 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs' parsed in 0 milliseconds ms, now saving
[2019-02-13 08:57:01] DEBUG inventory-processing - Inventory 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs' for node 'ad29bd41-9e07-47c4-a237-fc9b60ea37ae' pre-processed in 41 milliseconds ms
[2019-02-13 08:57:01] DEBUG inventory-processing - Inventory 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs' for node 'ad29bd41-9e07-47c4-a237-fc9b60ea37ae' pre-processed in 79 milliseconds ms
[2019-02-13 08:57:01] DEBUG inventory-processing - Report saved.
[2019-02-13 08:57:01] INFO  inventory-processing - Report 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs' for node 'agent1' [ad29bd41-9e07-47c4-a237-fc9b60ea37ae] (signature:certified) processed in 67 milliseconds ms
[2019-02-13 08:57:01] DEBUG inventory-processing - Report saved.
[2019-02-13 08:57:01] INFO  inventory-processing - Report 'AGENT1-ad29bd41-9e07-47c4-a237-fc9b60ea37ae.ocs' for node 'agent1' [ad29bd41-9e07-47c4-a237-fc9b60ea37ae] (signature:certified) processed in 61 milliseconds ms
[2019-02-13 08:57:02] INFO  scheduledJob - Update in node inventories main information detected: triggering a policy generation
[2019-02-13 08:57:02] INFO  com.normation.rudder.services.policies.PromiseGenerationServiceImpl - Start policy generation, checking updated rules
[2019-02-13 08:57:02] INFO  com.normation.rudder.domain.nodes.NodeInfo - Node 'agent1' (ad29bd41-9e07-47c4-a237-fc9b60ea37ae) is a Dsc node and a we do not know how to generate a hash yet

everything does look good though

after a while, i cnanot reproduce it. It happened with a DSC agent - but then it was correctly processed

Actions

Also available in: Atom PDF