Project

General

Profile

Actions

Bug #17390

closed

Root inventory is not processed after install

Added by Félix DALLIDET over 4 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
N/A
Category:
Server components
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Priority:
100
Name check:
To do
Fix check:
To do
Regression:

Description

On a 6.1-beta3, after my server install, the compliance and the inventory of the root server were off.
Looking in the inventory folders, my root server inventory was there:

server:/var/rudder/inventories # tree
.
├── accepted-nodes-updates
│   ├── server-root.ocs.gz
│   ├── server-root.ocs.sign
│   └── uuid.hive
├── failed
├── incoming
└── received


Unzipping it, solved the issue, the webapp immediatly processed it and my inventory and compliance went instantly ok.
I have no clue on why the inventory hook did not seem to trigger on this one.


Related issues 4 (0 open4 closed)

Related to Rudder - Bug #15433: Sometimes, somes inventories are received as .ocs.gz, and not handled by the webappRejectedActions
Related to Rudder - Bug #14627: Sometimes, root server shows up with "No machine inventory" after installReleasedFrançois ARMANDActions
Related to Rudder - Bug #15655: After installation, root server OS is listed as "other Linux" in the web interfaceResolvedActions
Is duplicate of Rudder - Bug #15422: Some inventories are not correctly noticed by inotify file watcherReleasedVincent MEMBRÉActions
Actions

Also available in: Atom PDF