Actions
Bug #16200
closedBug #16199: Missing timing info in logs for Home Page
Missing timing info in compliance computation logs
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Error - Fixed
Regression:
Description
Parent ticket exhibits that compliance computation is not always correctly traced
Updated by Nicolas CHARLES about 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2613
Updated by Nicolas CHARLES about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|bf77882a487492859a5a11e930dd60da33084af5.
Updated by François ARMAND about 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset about 5 years ago
- Subject changed from missing timing info in complince computation to Missing timing info in compliance computation logs
- Name check changed from To do to Reviewed
Updated by Nicolas CHARLES about 5 years ago
- Related to Bug #16256: Deadlock on compliance computing added
Updated by Nicolas CHARLES about 5 years ago
- Fix check changed from Checked to Error - Blocking
Updated by François ARMAND about 5 years ago
- Fix check changed from Error - Blocking to Error - Fixed
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.
Actions