Actions
Bug #7821
closed
Unexpected reports on "Check jetty process" component of system techniques
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
If jetty is restarted because one of the applications (endpoint or webapp) weren't reponding, we'll get a duplicate report for this component:
Files
Updated by Jonathan CLARKE about 8 years ago
- Related to Bug #7813: Reporting in server-components missing when restarting some services (ie jetty) added
Updated by Jonathan CLARKE about 8 years ago
The cause for this is that the bundle that detects an application is not responding (in server-roles/1.0/alive-check.st) calls a "generic" bundle named "generic_process_check_process" to force restart it, although this bundle is the one that provides reporting for the actual process checks.
Updated by Jonathan CLARKE about 8 years ago
- Status changed from New to In progress
Updated by Jonathan CLARKE about 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/857
Updated by Jonathan CLARKE about 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-techniques|bf4c90baf03dd5db6f188aef87136f20606fc6c6.
Updated by Vincent MEMBRÉ about 8 years ago
- Status changed from Pending release to Released
Actions