Actions
Bug #24362
closed
Bad certificate in a node makes rudder impossible to start
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
In 8.1, if a node has a corrupted certificate, then Rudder doesn't start.
This seems to be because we read all information from LDAP at start and stop on error in place of either loading the node with diminished capacities, or ignoring it.
Updated by François ARMAND 9 months ago
- Status changed from New to Rejected
I wasn't able to reproduce it with bad certificate, I correctly get an error at generation, but not something that forbids rudder to start.
Actions