Actions
Bug #19394
closed
When a node is totally deleted, cache in NodeInfoService can't know about it
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
If we delete-erase a node, without any other changes, nodeinfoservice won't know about it as there are no entry with modified time, so cache won't refresh, so node remain in the cache
we should add a "delete" method when a node is removed
Updated by Nicolas CHARLES over 3 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES over 3 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/3665
Updated by François ARMAND over 3 years ago
- Related to User story #18035: API to totally erase a node everywhere added
Updated by Nicolas CHARLES over 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|daff626876b69988fd9b7979c1404a6f56ad7141.
Updated by Nicolas CHARLES over 3 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.14 and 6.2.8 which were released today.
Actions