Project

General

Profile

Actions
Copy link

Bug #7353

closed

Missing debuging information for explain_compliance

Added by François ARMAND about 9 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Web - Compliance & node report
Target version:
3.0.12
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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.

Actions
Copy link
 #1

Updated by François ARMAND about 9 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
Actions
Copy link
 #2

Updated by François ARMAND about 9 years ago

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

Updated by Vincent MEMBRÉ almost 9 years ago

  • Parent task deleted (#7336)
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 9 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.

Actions
Copy link

Also available in: Atom PDF