Bug #12693: Reporting context is not set correctly when using an iterator somewhere - Rudder - Issue Tracker

Actions

Copy link

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.

Status:

Released

Priority:

N/A

Assignee:

Benoît PECCATTE

Category:

Generic methods

Target version:

4.3.2

Pull Request:

https://github.com/Normation/ncf/pull...

Severity:

Major - prevents use of part of Rudder | no simple workaround

UX impact:

User visibility:

Operational - other Techniques | Technique editor | Rudder settings

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

When an iterator is used, the last evaluated value is used as context for the whole method.

This happens only in >4.3.

Subtasks 1 (0 open — 1 closed)

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES over 6 years ago

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

Actions

Copy link

Updated by Nicolas CHARLES over 6 years ago

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

Actions

Copy link

Updated by Benoît PECCATTE over 6 years ago

Related to Bug #12694: In Rudder 4.1, we cannot do reporting using a variable defined in a generic method added

Actions

Copy link

Updated by Benoît PECCATTE over 6 years ago

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