Actions
Feature #11181
closedDisplay errors encountered when importing classes in the UI
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
When importing puppet classes, if there is a parse error the UI will basically show no changes, rather than reporting that there was an error. The error is logged in the proxy's log, but it would be very helpful (at least to me) for that error to be pushed back up to the UI. We catch most errors at commit-time via syntax checking hooks, but every once in a while something slips through and inevitably results in someone spending a bunch of time troubleshooting that probably could have been saved if the error had been presented directly to the user.
Updated by Dominic Cleal over 9 years ago
- Is duplicate of Feature #7086: Puppet modules being skipped or failed to import should be reported or noticed by foreman. added
Updated by Dominic Cleal over 9 years ago
- Status changed from New to Duplicate
Thanks for the report, we're tracking this under #7086 and linked ticket(s).
Actions