Actions
Bug #20960
closed
Lower the log level of the "Skipping adding class [...] as its name is equal or longer than 1024" message
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
It is not really a problem (just a message that could be useful to troubleshoot a problem) and happens quite a lot with Rudder due to the way the reporting is handled (in case full class prefix length exceeds 1024 and we fall back on the old class prefix).
Let's set it to verbose level so that it is not visible in normal usage.
Updated by Alexis Mousset about 2 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset about 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2584
Updated by Alexis Mousset about 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|600417181370d22da37d3a873d2b112b75f4b661.
Updated by Nicolas CHARLES about 2 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.2.13, 7.0.2 and 7.1.0~rc1 which were released today.
Actions