Project

General

Profile

Bug #11270

"no report" explanation is not correct in node details

Added by François ARMAND 3 months ago. Updated 3 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Target version (plugin):
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
32

Description

In rudder, there is a grace period for when we get the last reports from a node before marking it as down ("no reports").

This grace period is (by implementation) one run period + 5 minutes. So with a frequency of one run every 5 minutes, that lead to a grace periode of about 10 minutes before marking the node missing.

But we are telling user that the grace period is "two runs", which is false, and so people expect 30+ minutes when period is 15min in place of 20+.

It is only in 3.1 as we remove the text in 4.1.

PastedGraphic-4.png (93.6 KB) François ARMAND, 2017-08-16 15:13

Associated revisions

Revision cf32482e
Added by François ARMAND 3 months ago

Fixes #11270: \"no report\" explanation is not correct in node details

History

#1 Updated by François ARMAND 3 months ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND

#2 Updated by François ARMAND 3 months 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/1721

#3 Updated by François ARMAND 3 months ago

  • Status changed from Pending technical review to Pending release

#4 Updated by Vincent MEMBRÉ 3 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.23, 4.1.7 and 4.2.0~rc1 which were released today.

Also available in: Atom PDF