Bug #2120
closed
Node not found lead to global promise generation error
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.
Updated by Jonathan CLARKE almost 13 years ago
- Target version changed from 2.4.0~alpha2 to 2.4.0~alpha3
Updated by Jonathan CLARKE almost 13 years ago
- Target version changed from 2.4.0~alpha3 to 2.4.0~alpha4
Updated by François ARMAND almost 13 years ago
- Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5
Updated by Jonathan CLARKE almost 13 years ago
- Target version changed from 2.4.0~alpha5 to 2.4.0~alpha6
Updated by François ARMAND over 12 years ago
- Target version changed from 2.4.0~alpha6 to 2.4.0~beta2
Updated by Nicolas PERRON over 12 years ago
- Target version changed from 2.4.0~beta2 to 2.4.0~beta3
2.4.0~beta2 has been released. This ticket must be moved to 2.4.0~beta3.
Updated by Nicolas PERRON over 12 years ago
- Target version changed from 2.4.0~beta3 to 2.4.0~beta4
This is not a blocking issue so I moved it to the next run.
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 2.4.0~beta4 to 24
This may have been fixed by an unrelated commit. This needs testing again, but either way, it's not high priority.
Updated by François ARMAND over 11 years ago
- Target version changed from 24 to Ideas (not version specific)
Updated by François ARMAND almost 10 years ago
- Status changed from New to Rejected
As of 2.10 and up, this is not the case anymore.