Project

General

Profile

Actions

Bug #8344

closed

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

Missing relevant information about why the compliance is what it is on node

Added by François ARMAND almost 8 years ago. Updated almost 8 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

In case like #8051, it would be much, much clearer if the information that we have with the log:

  <logger name="explain_compliance.root" level="trace" additivity="false">
    <appender-ref ref="OPSLOG" />
    <appender-ref ref="STDOUT" />
  </logger>

were also available directly on the UI. It would also be very helpful to have information when we have couple of missing/unexpected, telling us that most likelly, the agent is sending report for a different config id.

Actions #1

Updated by François ARMAND almost 8 years ago

  • Status changed from New to In progress
Actions #2

Updated by François ARMAND almost 8 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/1103
Actions #3

Updated by François ARMAND almost 8 years ago

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

Updated by Vincent MEMBRÉ almost 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.

Actions

Also available in: Atom PDF