Project

General

Profile

Actions
Copy link

Bug #26683

closed

Bug #26611: invalidateComplianceRequest get saturated with UpdateCompliance messages

Don't check for expiration nodes that just got new reports

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

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Performance and scalability
Target version:
8.2.6
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

In the scheduler looking for new reports, we also look for expired compliance.
But we don't avoid to expire compliance for nodes that just got reports.

Actions
Copy link
 #1

Updated by François ARMAND about 1 month ago

  • Status changed from New to In progress
Actions
Copy link
 #2

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 Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/6306
Actions
Copy link
 #3

Updated by Anonymous about 1 month ago

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

Updated by François ARMAND 11 days ago

  • Fix check changed from To do to Checked

It looks like compliance is still OK after that change.

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ 2 days ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.2.6 and 8.3.1 which were released today.

Actions
Copy link

Also available in: Atom PDF