Project

General

Profile

Actions
Copy link

Bug #25650

closed

Node in with no reports, pending and keep compliance lead to computation loop

Added by François ARMAND about 1 month ago. Updated about 1 month ago.

Status:
Released
Priority:
N/A
Assignee:
Clark ANDRIANASOLO
Category:
Web - Compliance & node report
Target version:
8.2.0~rc1
Pull Request:
https://github.com/Normation/rudder/p...
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.

Related issues 1 (1 open — 0 closed)

Related to Rudder - Architecture #24963: Persist compliance in base to know last state for a long timePending releaseFrançois ARMANDActions
Actions
Copy link
 #1

Updated by François ARMAND about 1 month ago

  • Related to Architecture #24963: Persist compliance in base to know last state for a long time added
Actions
Copy link
 #2

Updated by François ARMAND about 1 month ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions
Copy link
 #3

Updated by François ARMAND about 1 month 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
Actions
Copy link
 #4

Updated by Anonymous about 1 month ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.2.0~rc1 which was released today.

Actions
Copy link

Also available in: Atom PDF