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 over 7 years ago. Updated over 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

Also available in: Atom PDF