Project

General

Profile

Actions

Bug #6211

closed

If a run is not completed, compliance computation goes mad

Added by François ARMAND about 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

If a run is not complete (i.e, we don't have the "end run" report), then the compliance computation for the node goes made and report everything missing and/or unexpected.

The technical problem seems to be that the non complete run should be ignored and is taken into account. As we don't have the end report, the run is seen as not having a configuration ID. So Rudder thinks it's a run from an agent before 3.0, look what could be the expected configuration for it (a very old one, the first with a configuration ID), and see that nothing matches: either the configuration expired a lot of time ago, or only a few or none of the expected reports matche the ones received.

Actions #1

Updated by François ARMAND about 6 years ago

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

Updated by François ARMAND 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