Project

General

Profile

Bug #7743

Compliance take into account expired run

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

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

Description

On a Rudder node that wasn't up since several month (but was running good at that time), we are getting full success compliance. If we are adding new nodes, system rules for the down node switch to pending, and then, in place of going to "no reports", go back to success.

The associated logs are:

[2016-01-08 13:51:01] DEBUG com.normation.rudder.services.nodes.NodeInfoServiceCachedImpl - NodeInfo cache is up to date, last modification time: '2016-01-08T13:31:57.000Z'
[2016-01-08 13:51:01] DEBUG explain_compliance.BB77117E-1DD1-4BC0-BEAD-5726E444B69E - Node run configuration: [BB77117E-1DD1-4BC0-BEAD-5726E444B69E:full-compliance, run interval: 5 min]
[2016-01-08 13:51:01] TRACE explain_compliance.BB77117E-1DD1-4BC0-BEAD-5726E444B69E - Computing compliance for node BB77117E-1DD1-4BC0-BEAD-5726E444B69E with: [Pending: until 2015-10-15T12:11:53.175Z expected NodeConfigId: -1980813546/[20
16-01-08T13:45:42.635Z-now] | last run: nodeConfigId: -1608019925/[2015-09-05T21:07:57.859Z-2015-10-15T12:01:53.175Z] received at 2015-09-05T21:31:08.000Z]
[2016-01-08 13:51:01] TRACE explain_compliance.BB77117E-1DD1-4BC0-BEAD-5726E444B69E - Node is Pending with reports from previous run, using merge/compare strategy between last reports from run -1608019925/[2015-09-05T21:07:57.859Z-2015-10-15T12:01:53.175Z] and expect reports -1980813546/[2016-01-08T13:45:42.635Z-now]
[2016-01-08 13:51:01] TRACE explain_compliance.BB77117E-1DD1-4BC0-BEAD-5726E444B69E - Compute compliance for node BB77117E-1DD1-4BC0-BEAD-5726E444B69E using: rules for which compliance is based on run reports: [5838ed25-50da-43a8-8519-7ae4af617527->0]; rule updated since run: [hasPolicyServer-root->12][inventory-all->12][32377fd7-02fd-43d0-aab7-28460a91347b->2]
[2016-01-08 13:51:01] DEBUG com.normation.rudder.services.reports.CachedReportingServiceImpl - Compliance cache miss (invalid version):[], cache miss (updated):[BB77117E-1DD1-4BC0-BEAD-5726E444B69E],  hit:[]
[2016-01-08 13:51:01] DEBUG com.normation.rudder.services.nodes.NodeInfoServiceCachedImpl - NodeInfo cache is up to date, last modification time: '2016-01-08T13:31:57.000Z'
[2016-01-08 13:51:01] DEBUG report - [Store Agent Run Times] Task #2800: Starting analysis for run times from 2016/01/08 13:50:56 up to 2016/01/08 13:51:01 (runs after SQL table ID 8760)

It may be the same root cause for #7336, because the agent wasn't sending reports from some time.


Related issues

Related to Rudder - Bug #7336: Node stuck in "Applying" statusRejectedFrançois ARMANDActions
Related to Rudder - Bug #8051: Compliance is not correctly computed if we receive run agent right after generationReleasedNicolas CHARLES2016-05-19Actions
#1

Updated by François ARMAND about 5 years ago

  • Related to Bug #7336: Node stuck in "Applying" status added
#2

Updated by François ARMAND about 5 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/1020
#3

Updated by François ARMAND about 5 years ago

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

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.13, 3.1.6 and 3.2.0 which were released today.

#5

Updated by Nicolas CHARLES almost 5 years ago

  • Related to Bug #8051: Compliance is not correctly computed if we receive run agent right after generation added

Also available in: Atom PDF