Project

General

Profile

Actions

Feature #22048

closed

ERF12-8219 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy,

Added by snow snow about 7 years ago. Updated over 6 years ago.

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

Description

The following error occurred when I tried to delete a host "ERF12-8219 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy, undefined method `auto_deletion' for #"

i install the chef-plugins with "foreman-installer \
--enable-foreman-plugin-chef \
--enable-foreman-plugin-tasks \
--enable-foreman-proxy-plugin-chef"

#i disable the chef use false
--chef.yml--
@---
:enabled: false
:chef_authenticate_nodes: false
:chef_server_url: https://foreman.j.com
  1. smart-proxy client node needs to have some admin right on chef-server
  2. in order to retrive all nodes public keys
  3. e.g. 'host.example.net'
    :chef_smartproxy_clientname: foreman.j.com
  4. e.g. /etc/chef/client.pem
    :chef_smartproxy_privatekey: /etc/chef/client.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@

I use the "Kickstart default" template as "Provisioning template". I found some configuration related to chef proxy in this template.
"chef_enabled = @host.respond_to?(:chef_proxy) && @host.chef_proxy"


Files

111.png View 111.png 38 KB snow snow, 12/26/2017 12:06 PM
222.png View 222.png 39 KB snow snow, 12/26/2017 12:08 PM
333.png View 333.png 12.1 KB snow snow, 12/26/2017 12:08 PM
444.png View 444.png 28.6 KB snow snow, 12/26/2017 12:09 PM
555.png View 555.png 11.6 KB snow snow, 12/26/2017 12:13 PM
Actions

Also available in: Atom PDF