Project

General

Profile

Actions

Bug #9231

closed

Exception message missing when ENC fails to render

Added by Dominic Cleal about 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
External Nodes
Target version:
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

Description

From http://projects.theforeman.org/issues/9185#note-3, when the ENC fails to render, the exception message isn't logged:

Failed to generate external nodes for host4.cloud.example.com with

It appears that refactoring in 4f7a4d0ba84f43e3cb0d422d9f5e82b01588f21b changed the logging message to use $ERROR_INFO instead of $!. This variable is only available if the 'English' library is loaded, which it doesn't appear to be.


Related issues 3 (0 open3 closed)

Related to Foreman - Bug #9185: Deleting a network interface breaks all puppet agent syncingResolved02/01/2015Actions
Related to Foreman - Feature #3809: Add rubocop to foremanClosedDavid DavisActions
Has duplicate Foreman - Bug #9305: ENC failures are not logged correctlyDuplicate02/10/2015Actions
Actions

Also available in: Atom PDF