Actions
Bug #16256
closedDeadlock on compliance computing
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
I generated policies, accepted nodes and the same time, and went to home page several time
after a while, compliance didn't show up...
running jstack show that a lot of thread are BLOCKED (see attachement)
Files
Updated by Nicolas CHARLES over 5 years ago
- Related to Bug #16200: Missing timing info in compliance computation logs added
Updated by Nicolas CHARLES over 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 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/2632
Updated by Nicolas CHARLES over 5 years ago
- Status changed from Pending technical review to Pending release
Updated by Alexis Mousset over 5 years ago
- Subject changed from Deadlock on compliance on Rudder 5.0 to Deadlock on compliance computing
- Name check changed from To do to Reviewed
Actions