Project

General

Profile

Actions
Copy link

Bug #2120

closed

Node not found lead to global promise generation error

Added by François ARMAND over 12 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
4
Assignee:
-
Category:
Web - Config management
Target version:
Ideas (not version specific)
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

During the deployment process, when a node is not found (for example, if a funny user deleted it from LDAP directly), the full process is stopped with an error.

It should only report a warning for the resulting process, log the corresponding error, but let promises be generated for other node.

Moreover, it is a difficult problem to solve for a simple user who doesn't want to go do dirty things in LDAP, so it should really be a work-aroundable situation.

Actions
Copy link

Also available in: Atom PDF