Project

General

Profile

Actions
Copy link

Bug #2877

closed

When a deployment is disallowed because of CFEngine check, no message is given about what is wrong

Added by François ARMAND over 11 years ago. Updated over 11 years ago.

Status:
Released
Priority:
3
Assignee:
Jonathan CLARKE
Category:
Web - Config management
Target version:
2.4.0~beta5
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

A deployment may be forbidden because we check the validity of the generated promises with cf-check.
But when that check is wrong, nothing useful is reported in the deployment box, and so the user does not have any way to correct what is wrong.

That seems almost a blocker for the final for me, because if not corrected, that imply that user will need a deep knowledge of cfengine and what could have been wrong with the last modification they did to resolve that kind of erroneous deployment. (ex: the use of a "\" in a directive property may lead to such errors, or #2041).

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #3538: When a deployment fails, error message may be emptyReleasedFrançois ARMAND2013-04-25Actions
Actions
Copy link

Also available in: Atom PDF