Should produce a proper error message instead of crashing

I also saw this when the foreman-proxy service was stopped, and I attempted to retrieve a certificate list.

Backtrace:

NoMethodError
undefined method `gsub' for #<ActiveRecord::RecordNotFound: ActiveRecord::RecordNotFound>
app/controllers/application_controller.rb:172:in `error'
app/controllers/puppetca_controller.rb:17:in `rescue in index'
app/controllers/puppetca_controller.rb:7:in `index'
app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'
lib/middleware/catch_json_parse_errors.rb:9:in `call'

I was just seeing this same behavior with Foreman 1.5.1 and Puppet 3.6.2. Solved it by adding the following to my client's auth.conf (/etc/puppet/auth.conf)

1. Allow puppet kick access
   path /run
   method save
   auth any
   allow *

"run puppet" feature now works a treat.

I should add that in the client log I saw the following:

Tue Jul 15 20:09:29 +0000 2014 Puppet (warning): Denying access: Forbidden request: puppet.example.com(<ip_address>) access to /run/hostname.example.com [save] authenticated at :119
Tue Jul 15 20:09:29 +0000 2014 Puppet (err): Forbidden request: puppet.example.com(<ip_address>) access to /run/hostname.example.com [save] authenticated at :119