Actions
Bug #7975
closed
Wrong reporting in servicesManagement 3.0
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Reporting is broken in servicesManagement 3.0.
Updated by Alexis Mousset almost 9 years ago
- Status changed from New to In progress
Updated by Alexis Mousset almost 9 years ago
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 almost 9 years ago
- 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
Updated by Alexis Mousset almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-techniques|ea8dd328300427beacc91cc4d9ee84b27a642d5a.
Updated by Nicolas CHARLES almost 9 years ago
- Related to Bug #8033: Typo in services management added
Updated by Vincent MEMBRÉ over 8 years ago
- Related to deleted (Bug #8033: Typo in services management)
Updated by Vincent MEMBRÉ over 8 years ago
- Status changed from Pending release to Released
Actions