Bug #9530: Each policy generation lead to a new nodeconnfigid even without promise written - Rudder - Issue Tracker

Actions

Copy link

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

Added by François ARMAND about 8 years ago. Updated about 8 years ago.

Status:

Released

Priority:

N/A

Assignee:

Vincent MEMBRÉ

Category:

Web - Compliance & node report

Target version:

4.0.0~rc4

Pull Request:

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

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.

Actions

Copy link

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.

Actions

Copy link

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".

Actions

Copy link