Actions
Bug #1466
closed
Rudder should halt on fatal errors during initialization
Status:
Rejected
Priority:
4
Assignee:
-
Category:
Web - Maintenance
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Currently, logs are very confusing in case an error occurs during startup of the application (ie, the LDAP server could not be contacted) because the error message appears, then many other errors appear, as Rudder does not halt on the first error.
This should be modified so that Rudder halts immediately, and the last log line contains only the real error message.
Updated by Jonathan CLARKE over 13 years ago
- Target version changed from 16 to 10
Updated by François ARMAND about 13 years ago
- Target version changed from 10 to 18
Updated by François ARMAND about 13 years ago
- Target version changed from 18 to 24
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 24 to Ideas (not version specific)
Updated by Jonathan CLARKE almost 12 years ago
- Category changed from 11 to Web - Maintenance
Updated by Jonathan CLARKE about 10 years ago
- Status changed from 8 to Rejected
This is a duplicate of #1974.
Updated by François ARMAND over 4 years ago
- Related to Architecture #17180: Compliance incorrectly computed with old reports or runs not sent in node chronological order added
Actions