Feature #7086
open
Puppet modules being skipped or failed to import should be reported or noticed by foreman.
Description
The issue is if you have a syntax error within a puppet module, or even a general error that prevents foreman from using it. It should be shown as a notice ( not an error since this should be a graceful failure to import ).
I imported a module, with a silly mistake, which could have been avoided through the use of the puppet agent itself. However in lieu of modules I create it would be good to know if a module pulled from a third party source was faulty instead of indicating nothing has changed or happened.
Updated by Dominic Cleal over 10 years ago
- Related to Bug #3900: Class removed because invalid syntax validation added
Updated by Dominic Cleal over 9 years ago
- Has duplicate Feature #11181: Display errors encountered when importing classes in the UI added
Updated by Dominic Cleal about 8 years ago
- Status changed from New to Duplicate
Thanks for the report, I'm closing to close this in order to combine it with #3900 which ought to be possible to fix now.
Updated by Dominic Cleal about 8 years ago
- Status changed from Duplicate to New
- Priority changed from Low to Normal
Correction: I'm reopening it as #3900 is a more complex requirement, since it may need some memorising of which class was imported from where, so when a syntax error occurs it can skip classes originally imported from the file with the error.
#15095 provides a classes_and_errors API in the smart proxy which includes error information in the response. This includes syntax and permission errors (#2289).
Note that the API will return a different response format and is only available on certain versions. It will return a 501 response if it isn't usable, so in that case, the original classes API should be used instead.