Project

General

Profile

Actions

Bug #19978

closed

Chef Plugin: [foreman-tasks/action] [E] ERF12-0944 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy, 500 Internal Server Error (ForemanChef::ProxyException)

Added by Dmitry Okun almost 7 years ago. Updated almost 6 years ago.

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

Description

While creating a host in Foreman and setting the CHEF proxy field, I run into the following issue error:

[foreman-tasks/action] [E] ERF12-0944 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy, 500 Internal Server Error (ForemanChef::ProxyException)

  1. cat /etc/foreman-proxy/settings.d/chef.yml
    ---
    :enabled: true
    :chef_authenticate_nodes: true
    :chef_server_url: https://<ip>/organizations/set
  2. smart-proxy client node needs to have some admin right on chef-server
  3. in order to retrive all nodes public keys
  4. e.g. 'host.example.net'
    :chef_smartproxy_clientname: <name>
  5. e.g. /etc/chef/client.pem
    :chef_smartproxy_privatekey: /etc/chef/<name>.pem
  1. turning of chef_ssl_verify is not recommended as it turn off authentication
  2. you can try set path to chef server certificate by chef_ssl_pem_file
  3. before setting chef_ssl_verify to false
  4. note that chef_ssl_pem_file must contain both private key and certificate
  5. because chef-api 0.5 requires it
    :chef_ssl_verify: false
  6. :chef_ssl_pem_file: /path

http://debugs.theforeman.org/foreman-debug-PSsPy.tar.xz

Also, please note, when enabling the Foreman Plugin, I run into the following issue: [Foreman - Bug #19660 ]


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #19660: VMware host creation fails with "undefined method `resourcePool' for #<RbVmomi::VIM::Folder:...>"Rejected05/24/2017Actions
Actions #1

Updated by Tomer Brisker almost 7 years ago

  • Project changed from Foreman to Chef
  • Category deleted (Plugin integration)
Actions #2

Updated by Marek Hulán almost 7 years ago

  • Priority changed from Urgent to Normal
  • Difficulty deleted (easy)

I'm sorry but the foreman-debug already expired. Could you please upload the log from proxy again? Feel free to just tail the file while you reproduce the problem. Also the full trace from Foreman production.log might help. My wild guess is that the plugin on Foreman proxy is misconfigured.

Actions #3

Updated by Anonymous almost 7 years ago

  • Related to Bug #19660: VMware host creation fails with "undefined method `resourcePool' for #<RbVmomi::VIM::Folder:...>" added
Actions #4

Updated by Anonymous almost 7 years ago

Dmitry, what's the status here?

Actions #5

Updated by Anonymous over 6 years ago

  • Status changed from New to Feedback
Actions #6

Updated by Dmitry Okun over 6 years ago

  • Status changed from Feedback to New

Michael Moll wrote:

Dmitry, what's the status here?

he tarball has been uploaded, please contact us on our mailing list or IRC
referencing the following URL:

http://debugs.theforeman.org/.tar.xz
Actions #7

Updated by Marek Hulán over 6 years ago

  • Status changed from New to Closed
  • translation missing: en.field_release set to 216

According to the trace, it was failing in validation bootstrap method since there was wrong setting name used. This should be fixed in 0.6.0 release. Please let me know/open a new issue in case it still does not work in this version.

Actions

Also available in: Atom PDF