Actions
Bug #13916
closed
After changing node hostname, old inventory with incorrect name is not deleted and sent to Rudder server
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
99
Name check:
Fix check:
Regression:
Description
After changing a node's hostname, I get the following issue:
- The old inventory is kept in
/var/rudder/tmp/inventories - When a new inventory is created, it is placed next to the old one in
/var/rudder/tmp/inventories - Both inventories are sent to the server
- The wrong inventory is treated after the good, one, so the hostname (and possibly other changes) never gets updated in the server.
We need to clean old inventories on the agent to avoid such behavior.
Setting to major as it may hide important inventory updates.
Updated by Alexis Mousset almost 6 years ago
- Translation missing: en.field_tag_list set to Sponsored
Updated by Alexis Mousset almost 6 years ago
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 113
Updated by Alexis Mousset almost 6 years ago
A workaround is to remove the old inventory from /var/rudder/tmp/inventories and run rudder agent inventory again.
Updated by François ARMAND almost 6 years ago
- Assignee set to Benoît PECCATTE
We wanted to keep one inventory for debuging. If hostname changes, then the newly generated inventory does not override the old one, and both are sent to Rudder. This cause chaos.
We need to specify the exhaustive list of filename to send to Rudder (ie inventory file + signature file).
We don't need to erase old file.
Updated by Benoît PECCATTE almost 6 years ago
- Target version set to 5.0.4
- the fix will conflict with fusion < 2.3
- fusion < 2.3 is found in very old systems
- fusion >= 2.3 is found in not too old systems
- system fusion is used in rudder agent thin
- rudder agent thin is still supported until rudder 4.3
- rudder server 5.0 must support agent >= 4.1
So we choose to potentially break old agent only on 5.0
Updated by Benoît PECCATTE almost 6 years ago
- Status changed from New to In progress
Updated by Benoît PECCATTE almost 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1377
Updated by Benoît PECCATTE almost 6 years ago
- Status changed from Pending technical review to Pending release
Updated by Vincent MEMBRÉ almost 6 years ago
- Subject changed from Old incorrect inventory is still used on a node to After changing node hostanme, old inventory with incorrect name is not deleted and sent to Rudder server
- Priority changed from 113 to 112
Updated by Vincent MEMBRÉ almost 6 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.4 which was released today.
Changelog
Updated by François ARMAND almost 6 years ago
- Subject changed from After changing node hostanme, old inventory with incorrect name is not deleted and sent to Rudder server to After changing node hostname, old inventory with incorrect name is not deleted and sent to Rudder server
- Priority changed from 112 to 111
Actions