Project

General

Profile

Actions

Architecture #19920

closed

root inventory is missing and need to be resent after install

Added by François ARMAND about 3 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:

Description

Even after correction of #17390 and related tickets, we still have cases where after a fresh installation, rudder root server inventory information is missing.

As far as we know, in that case, we don't have any relevant logs, but we suspect that it can happen when rudder-jetty restart in the middle of inventory processing, just after the inventory was moved from /var/rudder/inventories/incoming to /var/rudder/inventories/received but before it's full saved in LDAP.

Workaround for 6.1/6.2/7.0: on the root server, do: rudder agent inventory

Solution: we need to rework inventory-processing so that all inventories, even the one coming from the inventory API, go to the incoming directory, and then only move inventories to received once they are fully saved so that if a restart occures before that point, they will be reprocessed at next startup.


Related issues 4 (0 open4 closed)

Related to Rudder - Bug #19585: Sometime inventory processing is not done when inventory is receveivedReleasedNicolas CHARLESActions
Related to Rudder - Bug #15655: After installation, root server OS is listed as "other Linux" in the web interfaceResolvedActions
Related to Rudder - Bug #20994: Some inventories are stuck in the incoming folderResolvedActions
Related to Rudder - Bug #22099: Missing error log for inventory with bad signatureReleasedVincent MEMBRÉActions
Actions

Also available in: Atom PDF