Project

General

Profile

Actions

Bug #9862

closed

Exception is raised If chef server is unavailable and host deletion is triggered

Added by Marek Hulán about 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
foreman_chef
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

In plan phase we check whether the node and client exist. On smart proxy we don't treat exception Errno::EHOSTUNREACH - No route to host - connect(2) which results on 500 response, on Foreman side leads also to 500

Here's the Foreman trace

2015-03-23 09:56:27 [E] 500 Internal Server Error (RestClient::InternalServerError)
/home/ares/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rest-client-1.6.8/lib/restclient/abstract_response.rb:48:in `return!'
/home/ares/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rest-client-1.6.8/lib/restclient/request.rb:269:in `process_result'
/home/ares/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rbovirt-0.0.35/lib/restclient_ext/request.rb:50:in `block in transmit'
/home/ares/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/net/http.rb:852:in `start'
/home/ares/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rbovirt-0.0.35/lib/restclient_ext/request.rb:44:in `transmit'
/home/ares/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rest-client-1.6.8/lib/restclient/request.rb:68:in `execute'
/home/ares/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rest-client-1.6.8/lib/restclient/request.rb:35:in `execute'
/home/ares/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rest-client-1.6.8/lib/restclient/resource.rb:51:in `get'
/home/ares/Projekty/Zdrojaky/foreman/lib/proxy_api/resource.rb:67:in `get'
/home/ares/Projekty/Zdrojaky/foreman_chef/app/lib/proxy_api/foreman_chef/chef_proxy.rb:28:in `show_node'
/home/ares/Projekty/Zdrojaky/foreman_chef/app/models/foreman_chef/smart_proxy_extensions.rb:7:in `show_node'
/home/ares/Projekty/Zdrojaky/foreman_chef/app/lib/actions/foreman_chef/host/destroy.rb:11:in `plan'


Related issues 1 (1 open0 closed)

Related to Chef - Bug #9863: Rescue from errors when chef server is unreachableNew03/23/2015Actions
Actions #1

Updated by Marek Hulán about 9 years ago

  • Related to Bug #9863: Rescue from errors when chef server is unreachable added
Actions #2

Updated by Marek Hulán about 9 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Marek Hulán
  • translation missing: en.field_release set to 46
  • Pull request https://github.com/theforeman/foreman_chef/pull/17 added
  • Pull request deleted ()

Since the raise happens in orchestration, everything is rollbacked. We only display red message but we don't render 500.

Actions #3

Updated by Marek Hulán almost 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF