Project

General

Profile

Actions

Bug #6209

closed

Some heartbeat are skipped in change only mode

Added by Nicolas CHARLES about 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

We define the heartbeat as a number of minute, as run length * interval
So, if we have a run every 5 minutes, and want a heartbeat each time, we define the heartbeat frequency to be 5 minutes

so, for 5 minutes, heartbeat are not sent.
If we consider two runs:
Run A, at 10:00, lasting 1 minutes
Run B, at 10:05, lasting 5 secondes

RunA will send its heartbeat at 10:01, for the run 10:00 -> 10:01
RunB will so not send any heartbeat, as 10:05 is before 10:01 + 5 minutes

Actions #1

Updated by Nicolas CHARLES about 6 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/810
Actions #2

Updated by Nicolas CHARLES about 6 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #4

Updated by Vincent MEMBRÉ about 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0, which was released on 2015/02/16

Actions

Also available in: Atom PDF