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.
Updated by François ARMAND over 11 years ago
- Status changed from 8 to In progress
- Assignee set to François ARMAND
Updated by François ARMAND over 11 years ago
- Status changed from In progress to Pending release
- % Done changed from 0 to 100
Applied in changeset c3cbeeef2c42bb252519f6fc021ce6cf718220a2.
Updated by Vincent MEMBRÉ over 11 years ago
Applied in changeset b9d9c296c7472230cdde042e29d0d84bcb79916c.
Updated by François ARMAND over 11 years ago
Applied in changeset 0bdf0ab0eec827be2b98b47f727ae115177a133d.
Updated by François ARMAND over 11 years ago
Applied in changeset 7a2963fb2b63f27f05b1cd69017344ad78028949.
Updated by François ARMAND over 11 years ago
- Pull Request set to https://github.com/Normation/rudder/pull/193
Updated by Nicolas PERRON over 11 years ago
- Status changed from Pending release to Released
Actions