Project

General

Profile

Actions

Bug #11270

closed

"no report" explanation is not correct in node details

Added by François ARMAND over 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
32
Name check:
Fix check:
Regression:

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.


Files

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

Updated by François ARMAND over 7 years ago

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

Updated by François ARMAND over 7 years 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
Actions #3

Updated by François ARMAND over 7 years ago

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

Updated by Vincent MEMBRÉ about 7 years 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.

Actions

Also available in: Atom PDF