Project

General

Profile

Bug #6746

Heartbeat bad interval time calcul on node

Added by Francois BAYART over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
2
Category:
Web - Nodes & inventories
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

I use compliance mode as Changes only, my global agent run schedule is 1 hour and the global "send heartbeat every" option is 1 run.

In "Administration / Settings / AGENT RUN HEARTBEAT" I have : "Heartbeat will be sent every 60 minutes"

When I look node details and I go on "parameters", the "agent run heartbeat" section indicate a bad interval period, it seems to use the information like override is checked but it isn't.

Nodes / parameters / agent run heartbeat:
The current global setting is to run every 1 runs, (so every 5 minutes).
Heartbeat will be sent every 5 minutes

#1

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.0.5 to 3.0.6
#2

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.0.6 to 3.0.7
#3

Updated by Nicolas CHARLES over 5 years ago

Francois,

I can't reproduce this issue; i've got the following text

The current global setting is to run every hour, starting at 00:00, with a maximum delay after scheduled run time (random interval) of 00:04.
You may override this global setting just for this node below:

The dropdownlist are indeed confusing (it says 5 minutes), but text is valid

What would be the step to reproduce ?

#4

Updated by Nicolas CHARLES over 5 years ago

oh my bad, I didn't read correctly, the heartbeat section is indeed invalid

In "changes only" compliance mode, the agent will report a "heartbeat" when no other events are reported (no errors and no repairs). This frequency can be changed to send a heartbeat only every N runs.
This setting is defined as a default for all nodes in the global Settings.
The current global setting is to run every 2 runs, (so every 10 minutes).

#5

Updated by Nicolas CHARLES over 5 years ago

  • Priority changed from N/A to 2

generated promises have a correct heartbeat value, so it is only a display error

#6

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
#7

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/887
#8

Updated by Nicolas CHARLES over 5 years ago

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

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.7 and 3.1.0 which were released today.

Also available in: Atom PDF