Actions
Bug #19414
closed
Inventory with updated properties doesn't always start a policy generation
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
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
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
Updated by 
Updated by 
Updated by
Actions