Bug #7975: Wrong reporting in servicesManagement 3.0 - Rudder - Issue Tracker

Actions

Copy link

Bug #7975

closed

Wrong reporting in servicesManagement 3.0

Bug #7975: Wrong reporting in servicesManagement 3.0

Added by Alexis Mousset over 9 years ago. Updated over 9 years ago.

Status:

Released

Priority:

N/A

Assignee:

Benoît PECCATTE

Category:

Techniques

Target version:

2.11.19

Pull Request:

https://github.com/Normation/rudder-t...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

Reporting is broken in servicesManagement 3.0.

Subtasks 1 (0 open — 1 closed)

Updated by Alexis Mousset over 9 years ago Actions
Copy link
#1

Status changed from New to In progress

Updated by Alexis Mousset over 9 years ago Actions
Copy link
#2

The problem comes from canonified string expressions like:

canonify("check_process_range_${index}.defined_process_name_${index}.${service[${index}][canon_name]}_out_of_range.service_restart_${service[${index}][name]}_repaired");

Updated by Alexis Mousset over 9 years ago Actions
Copy link
#3

Status changed from In progress to Pending technical review
Assignee changed from Alexis Mousset to Benoît PECCATTE
Pull Request set to https://github.com/Normation/rudder-techniques/pull/878

PR https://github.com/Normation/rudder-techniques/pull/878