Project

General

Profile

Actions

Bug #12003

closed

"RuntimeError: Could not get facts from proxy", on refreshing facts of a discovered host

Added by Sachin Ghai about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Category:
Discovery plugin
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I tried discovery via PXE and host discovered successfully. However when I tried to refresh its facts from webUI, following error appeared:

Oops, we're sorry but something went wrong

Warning!
Could not get facts from proxy https://192.168.100.40:8443: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

production.log:
------------------

 | Started GET "/discovered_hosts/mac5254000c882d/refresh_facts" for 10.65.193.85 at 2015-09-30 02:28:09 -0400
2015-09-30 02:28:09 [app] [I] Processing by DiscoveredHostsController#refresh_facts as HTML
2015-09-30 02:28:09 [app] [I]   Parameters: {"id"=>"mac5254000c882d"}
2015-09-30 02:28:09 [app] [W] Action failed
 | RuntimeError: Could not get facts from proxy https://192.168.100.40:8443: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
 | /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_discovery-4.1.0/app/models/host/discovered.rb:139:in `rescue in refresh_facts'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_discovery-4.1.0/app/models/host/discovered.rb:136:in `refresh_facts'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_discovery-4.1.0/app/controllers/discovered_hosts_controller.rb:64:in `refresh_facts'
 | /opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
 | /opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/abstract_controller/base.rb:167:in `process_action'
 | /opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_controller/metal/rendering.rb:10:in `process_action'
 | /opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/abstract_controller/callbacks.rb:18:in `block in process_action'
 | /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:649:in `block (4 levels) in _run__763447183888497241__process_action__2380366033559342217__callbacks'

I'm trying discovery via direct connection and not using proxy but still error statement using 8443 port as below:

Could not get facts from proxy https://192.168.100.40:8443:

Here 192.168.100.40 is the assigned IP of discovered host.

Build version:
--------------
tfm-rubygem-foreman_discovery-4.1.0-1.fm1_10.git.56.4380f1d.git.56.4380f1d.git.56.4380f1d.el7.noarch
foreman-release-1.10.0-0.develop.201509171905gitd7b8c7a.el7.noarch
foreman-libvirt-1.10.0-0.develop.201509171905gitd7b8c7a.el7.noarch
foreman-1.10.0-0.develop.201509171905gitd7b8c7a.el7.noarch
discovery image tar fdi-image-3.0.1.iso


Related issues 1 (0 open1 closed)

Related to Discovery - Tracker #10294: PXEless discovery featureClosedLukas Zapletal04/28/2015

Actions
Actions #1

Updated by Sachin Ghai about 9 years ago

Actions #2

Updated by Lukas Zapletal about 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Lukas Zapletal

Valid bug, regression. Image is now https and this cannot be used for facts retrieval. Since we no longer use BMC API, we can get rid of FACTER API as well and move the call into our new discovery_image plugin now.

Actions #3

Updated by The Foreman Bot about 9 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_discovery/pull/223 added
  • Pull request deleted ()
Actions #4

Updated by Anonymous about 9 years ago

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

Also available in: Atom PDF