Project

General

Profile

Actions

Bug #11819

closed

Missing node id in log message on generaction error

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

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

When a node policy can not be generated because of a configuration problem, we don't have the node id / hostname, which is quite a problem to try to understand where is the problem.

Actions #1

Updated by François ARMAND about 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1808
Actions #2

Updated by François ARMAND about 7 years ago

  • Status changed from Pending technical review to Pending release
Actions #3

Updated by Vincent MEMBRÉ about 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.9 and 4.2.3 which were released today.

Actions

Also available in: Atom PDF