Project

General

Profile

Actions

Bug #9458

closed

User story #1808: Add an Audit mode to Rudder: only check properties, no modification on nodes

Invalid display in compliance for non-compliant report: shows "Not applicable" when not compliance

Added by Nicolas CHARLES over 7 years ago. Updated over 7 years ago.

Status:
Released
Priority:
1
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On the node "compliance reports" page and rules compliance, when going to the drill down of the reports, it shows "Not applicable" rather than Non compliance, see screenshot

Note: the compliance logger isn't helpful at all

2016-10-19 10:35:15] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Run config for node 8b43e849-f0a3-499c-88bc-da6414dc4e38: ComputeCompliance : Last run at 2016-10-19T10:31:05.000Z is for the correct configId 27abc96d and not expired, compute compliance
[2016-10-19 10:35:15] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Computing compliance for node 8b43e849-f0a3-499c-88bc-da6414dc4e38 with: [ComputeCompliance: expected NodeConfigId: 27abc96d/[2016-10-19T10:14:49.829Z-now] | last run: nodeConfigId: 27abc96d received at 2016-10-19T10:31:05.000Z | expired at 2016-10-19T10:41:05.000Z]
[2016-10-19 10:35:15] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Using merge/compare strategy between last reports from run at 2016-10-19T10:31:05.000Z and expect reports 27abc96d/[2016-10-19T10:14:49.829Z-now]
[2016-10-19 10:35:15] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Compute compliance for node 8b43e849-f0a3-499c-88bc-da6414dc4e38 using: rules for which compliance is based on run reports: [ffb7c92e-a561-4300-b17d-a680ff8152fc->1][inventory-all->7][hasPolicyServer-root->7][32377fd7-02fd-43d0-aab7-28460a91347b->2]; rule updated since run: []
[2016-10-19 10:36:08] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Run config for node 8b43e849-f0a3-499c-88bc-da6414dc4e38: ComputeCompliance : Last run at 2016-10-19T10:36:00.000Z is for the correct configId 27abc96d and not expired, compute compliance


Files

compliance.png (26 KB) compliance.png Nicolas CHARLES, 2016-10-19 12:37
Actions #1

Updated by Nicolas CHARLES over 7 years ago

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

Updated by Nicolas CHARLES over 7 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/1306
Actions #3

Updated by Nicolas CHARLES over 7 years ago

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

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 318 to 4.0.0~rc2
Actions #5

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.0~rc2 to 4.0.0~rc1
Actions #6

Updated by Vincent MEMBRÉ over 7 years ago

  • Parent task set to #1808
Actions #7

Updated by Alexis Mousset over 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.

Actions

Also available in: Atom PDF