Actions
Bug #17441
closed
Ignored node lead to an error log during generation
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
That log should say that it's likely because node is ignored/disabled, and it should be only info level.
Updated by François ARMAND over 4 years ago
- Status changed from New to In progress
Updated by François ARMAND over 4 years ago
even debug level, I'm not sure why we would like to see tens of info line at each generation about ignored nodes.
Updated by François ARMAND over 4 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/2984
Updated by François ARMAND over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d4e42c0f57674144101d21d656b047a8e6449f1e.
Updated by François ARMAND over 4 years ago
Applied in changeset rudder|f2678ac7ae136801e81c6c2b2b45ad082a131b40.
Updated by Vincent MEMBRÉ over 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.18 and 6.1.2 which were released today.
Actions