Project

General

Profile

Actions

Bug #3538

closed

When a deployment fails, error message may be empty

Added by François ARMAND almost 10 years ago. Updated over 9 years ago.

Status:
Released
Priority:
3
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
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.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #2877: When a deployment is disallowed because of CFEngine check, no message is given about what is wrongReleasedJonathan CLARKE2012-09-08Actions
Actions #1

Updated by François ARMAND almost 10 years ago

  • Status changed from 8 to In progress
  • Assignee set to François ARMAND
Actions #2

Updated by François ARMAND almost 10 years ago

  • Status changed from In progress to Pending release
  • % Done changed from 0 to 100
Actions #6

Updated by François ARMAND almost 10 years ago

  • Pull Request set to https://github.com/Normation/rudder/pull/193
Actions #7

Updated by Nicolas PERRON over 9 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF