Project

General

Profile

Bug #7353

Missing debuging information for explain_compliance

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

I'm stuck with the parent bug because I can't debug it correctly.

What we need is the possibility to add verbose debugging log for only one node. With that kind of logs, perhaps we could better understand what Rudder is doing.

#1

Updated by François ARMAND over 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/945
#2

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

  • Parent task deleted (#7336)
#5

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.12 and 3.1.5 which were released today.

Also available in: Atom PDF