Actions
Bug #25650
closed
Node in with no reports, pending and keep compliance lead to computation loop
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
If we have a node:
- which never send a report to rudder,
- with a keep compliance (perhaps only if set when the node is pending, ie after a reboot or a generation with changes for it)
- pending,
Then the compliance keep being computed every five seconds for that node, and its expiration date is forwarded 5s ahead each time.
Updated by François ARMAND 2 months ago
- Related to Architecture #24963: Persist compliance in base to know last state for a long time added
Updated by François ARMAND 2 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 2 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/5935
Updated by Anonymous 2 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|215d59b27fccc95b72b0a86825c2f52cdf17f622.
Updated by Vincent MEMBRÉ 2 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.0~rc1 which was released today.
Actions