Bug #12693
closed
Reporting context is not set correctly when using an iterator somewhere
Added by Alexis Mousset over 6 years ago.
Updated over 2 years ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Description
When an iterator is used, the last evaluated value is used as context for the whole method.
This happens only in >4.3.
we are setting the context via
"method_call_context" usebundle => _method_reporting_context("File absent", "/tmp/${variable.name}");
so all component values are iterated over, and the last one wins
As discussed with Alexis, the solution we found is to rewrite the report method in 4.3.
Each generic method will change the call to the log method, to include the component_value, so that it fixes this issue
We need to keep the previous implementation as well, for compatibility
- Related to Bug #12694: In Rudder 4.1, we cannot do reporting using a variable defined in a generic method added
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 52
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/ncf/pull/765
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.2 which was released today.
- Project changed from 41 to Rudder
- Category changed from Generic methods to Generic methods
- Priority changed from 52 to 0
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by