Pushing the "Certificates" button on a smart proxy with disabled PuppetCA throws cryptic ActiveRecord error
I think a more meaningful error message should be displayed. Something like: "This smart-proxy has certificate management disabled". I don't know if other errors in the dns, puppet or dhcp functionality are any more meaningful, but I think ActiveRecord errors are not the preferred messages to display.
#3 Updated by Dominic Cleal almost 8 years ago
- Status changed from New to Resolved
- Assignee deleted (
Thanks, I believe this is now resolved in Foreman 1.5.2. Errors like this are raised as standard Foreman exceptions, which should provide the response from the proxy with an error code which can be looked up on our wiki. The proxy logs will also detail the underlying cause.