Project

General

Profile

Actions

Bug #19414

closed

Inventory with updated properties doesn't always start a policy generation

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

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
76
Regression:

Description

Use case:
Node keys and certificate were updated for a node. It sent a new inventory, but there were no policy geneation, so it couldn't connect to the server to fetch new policies

But that problem exists with any property, because we only check is cache is upToDate every 30s. But the cache can be up to date (because it was updated for something else) and so we can miss a necessary policy generation.

Workaround: clear cache or make a policy change

Actions #1

Updated by François ARMAND over 1 year ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #2

Updated by François ARMAND over 1 year ago

  • Subject changed from When a node gets a new certificate, policies are not regenerated, so it can't connect to Inventory with updated properties doesn't always start a policy generation
  • Description updated (diff)
  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 76
Actions #3

Updated by François ARMAND over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/3675
Actions #4

Updated by François ARMAND over 1 year ago

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

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