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 12 years ago. Updated over 12 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
 #1

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.4.0~rc1 to 2.4.0~rc2
Actions
Copy link
 #2

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from New to 2
  • Assignee set to Nicolas CHARLES
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 12 years ago

  • Status changed from 2 to Pending technical review
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by François ARMAND over 12 years ago

  • Status changed from Pending technical review to Released
Actions
Copy link
 #5

Updated by François ARMAND over 12 years ago

  • Status changed from Released to Discussion
  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE

That seems technically OK.
Jon, do you want to look at the look'n'feel to see if the result is OK ?
Perhaps I would like to have a more obvious thing saying that "technical details" is clickable.

You can see an error by putting a " (double quote) in a MOTD directive message. The directive must be applied to at least one node.

Actions
Copy link
 #7

Updated by Nicolas CHARLES over 12 years ago

  • Status changed from Discussion to Pending technical review
Actions
Copy link
 #8

Updated by Nicolas PERRON over 12 years ago

  • Target version changed from 2.4.0~rc2 to 2.4.0~beta5
Actions
Copy link
 #9

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from Pending technical review to Released

François ARMAND wrote:

That seems technically OK.
Jon, do you want to look at the look'n'feel to see if the result is OK ?
Perhaps I would like to have a more obvious thing saying that "technical details" is clickable.

Looks good to me! Feel free to improve the UI if you like, but I think that should be in a different ticket now.

Actions
Copy link

Also available in: Atom PDF