Actions
Bug #3538
closedWhen a deployment fails, error message may be empty
Status:
Released
Priority:
3
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When a deployment fails due to a failing verification of cf-promises, the message should be added to the "details" pop-up.
But sometime, it is not, details contains:
=> Deployment error for process '13' at 2013/04/25 17:28:14 => Cannot write configuration node => Error when preparing rules for agents => The generated promises are invalid, cause is: Show technical details Technical details
And nothing more, each time cause or details are empty.
You can reproduce that bug with 2.5.* policies (so in a Rudder 2.5), whith the "Download a File" directive, and setting both mandatory path to an invalid value (I used "Download a File").
The bug seems to be also in Rudder 2.4.
Actions