Bug #9231
closed
Exception message missing when ENC fails to render
Added by Dominic Cleal almost 10 years ago.
Updated over 6 years ago.
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 to Bug #9185: Deleting a network interface breaks all puppet agent syncing added
There's another instance in app/models/host/managed.rb, so these either need reverting (and disable Style/SpecialGlobalVars in rubocop again) or require English from something core in config/.
- Assignee set to David Davis
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2131 added
- Pull request deleted (
)
- Has duplicate Bug #9305: ENC failures are not logged correctly added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 32
Also available in: Atom
PDF