Project

General

Profile

Actions

Bug #19394

closed

When a node is totally deleted, cache in NodeInfoService can't know about it

Added by Nicolas CHARLES over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
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


Related issues 1 (0 open1 closed)

Related to Rudder - User story #18035: API to totally erase a node everywhereReleasedNicolas CHARLESActions
Actions #1

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from New to In progress
Actions #2

Updated by Nicolas CHARLES over 1 year 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
Actions #3

Updated by François ARMAND over 1 year ago

Actions #4

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from Pending technical review to Pending release
Actions #6

Updated by Vincent MEMBRÉ over 1 year 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

Also available in: Atom PDF