Bug #19414: Inventory with updated properties doesn't always start a policy generation - Rudder - Issue Tracker

Actions

Copy link

Bug #19414

closed

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

Added by Nicolas CHARLES over 3 years ago. Updated over 3 years ago.

Status:

Released

Priority:

N/A

Assignee:

Nicolas CHARLES

Category:

Web - Config management

Target version:

6.1.14

Pull Request:

https://github.com/Normation/rudder/p...

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:

Name check:

To do

Fix check:

Checked

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

Copy link

Updated by François ARMAND over 3 years ago

Status changed from New to In progress
Assignee set to François ARMAND

Actions

Copy link

Updated by François ARMAND over 3 years 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