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
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 François ARMAND about 8 years ago
- Translation missing: en.field_tag_list set to Blocking 4.0
This is of course blocking 4.0.
Updated by François ARMAND about 8 years ago
Moreover, we weren't very smart in the way we are building the config version, because:
System.currentMillis + XXX.hashCode => that's the same 4 byte that are impacted, something like "System.currentMillis + XXX.hashCode.toLong<<4" would lead to a better distribution.
And we should use the generation time for the salt, so it is possible to find back the hash from the "beginDate".
Updated by François ARMAND about 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1340
Updated by François ARMAND about 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|96e3d778393ac09b2cc981bffef9bcd023a9bb6a.
Updated by Alexis Mousset about 8 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.