Actions
Bug #9530
closed
Bug #9518: When we just apply a configuration, reports is "missing" (not "pending")
Each policy generation lead to a new nodeconnfigid even without promise written
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In the parent task, we changed the way node config id are generated to have them unique, introducing a salt (current time).
The cache verification and everything works fine, but even WITHOUT cache invalidation, we are writting a new expected node configuration. As the promises are not written, this lead to a case were the node send reports for a given config id, but Rudder is expecting them for an other => error.
So it seems that somewhere we are a little to zealous about writting new expected configuration.
Updated by 
Updated by
Actions