Project

General

Profile

Actions

Bug #23140

open

smart-proxy page errors when puppet service stopped

Added by Thomas McKay about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

After stopping pupper.service and puppetserver.service on smart-proxy the web page errors and server throws 500 to logs. Stopping puppet should not be fatal, should it?

2018-04-05T23:55:11 [W|app|0e6fa] Failed to puppet_environments
 | Foreman::WrappedException: ERF50-5345 [Foreman::WrappedException]: Unable to connect ([ProxyAPI::ProxyException]: ERF12-2749 [ProxyAPI::ProxyException]: Unable to get environments from Puppet ([RestClient::NotAcceptable]: 406 Not Acceptable) for proxy https://registry.example.com:9090/puppet)
 | /home/vagrant/code/foreman/app/services/proxy_status/base.rb:55:in `rescue in fetch_proxy_data'
 | /home/vagrant/code/foreman/app/services/proxy_status/base.rb:47:in `fetch_proxy_data'
 | /home/vagrant/code/foreman/app/services/proxy_status/puppet.rb:4:in `environment_stats'
 | /home/vagrant/code/foreman/app/controllers/smart_proxies_controller.rb:61:in `puppet_environments'
 | /home/vagrant/.rvm/gems/ruby-2.4.1/gems/actionpack-5.1.4/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
 | /home/vagrant/.rvm/gems/ruby-2.4.1/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:186:in `process_action'

No data to display

Actions

Also available in: Atom PDF