Feature #22048
closed
ERF12-8219 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy,
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"
--chef.yml--
@---
:enabled: false
:chef_authenticate_nodes: false
:chef_server_url: https://foreman.j.com
- smart-proxy client node needs to have some admin right on chef-server
- in order to retrive all nodes public keys
- e.g. 'host.example.net'
:chef_smartproxy_clientname: foreman.j.com - e.g. /etc/chef/client.pem
:chef_smartproxy_privatekey: /etc/chef/client.pem
- turning of chef_ssl_verify is not recommended as it turn off authentication
- you can try set path to chef server certificate by chef_ssl_pem_file
- before setting chef_ssl_verify to false
- note that chef_ssl_pem_file must contain both private key and certificate
- because chef-api 0.5 requires it
:chef_ssl_verify: false - :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
Updated by Anonymous almost 7 years ago
- Project changed from Foreman to Chef
- Category deleted (
Plugin integration) - Difficulty deleted (
hard) - Assignee deleted (
Anonymous)
Please do not assign tickets to people out of the blue. Thanks.
Updated by Marek Hulán almost 7 years ago
- Status changed from New to Duplicate
- Translation missing: en.field_release set to 216
This is most likely incompatibility with Foreman 1.16, closing as a duplicate of #19620, please let us know if you use older version of Foreman. This should be fixed in upcoming 0.6.0 release
Updated by snow snow almost 7 years ago
- File 111.png 111.png added
- File 222.png 222.png added
- File 333.png 333.png added
- File 444.png 444.png added
- File 555.png 555.png added
Marek Hulán wrote:
This is most likely incompatibility with Foreman 1.16, closing as a duplicate of #19620, please let us know if you use older version of Foreman. This should be fixed in upcoming 0.6.0 release
Hi Marek Hulán Thank you for your recovery.
I have now reinstalled a foreman, and my system configuration and software configuration are as follows.
[root@foreman pxelinux.cfg]# yum -y update
....
[root@foreman pxelinux.cfg]# cat /proc/version
Linux version 3.10.0-693.11.1.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Mon Dec 4 23:52:40 UTC 2017
[root@foreman pxelinux.cfg]# ruby -v
ruby 2.0.0p648 (2015-12-16) [x86_64-linux]
[root@foreman foreman]# rpm -qa | grep foreman
tfm-rubygem-foreman_setup-5.0.0-1.fm1_13.el7.noarch
foreman-release-1.16.0-1.el7.noarch
tfm-rubygem-foreman-tasks-0.10.0-2.fm1_16.el7.noarch
tfm-rubygem-foreman_chef-0.5.0-1.fm1_15.el7.noarch
foreman-1.16.0-1.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.11.0-1.el7.noarch
foreman-selinux-1.16.0-1.el7.noarch
foreman-release-scl-3-1.el7.noarch
foreman-debug-1.16.0-1.el7.noarch
foreman-postgresql-1.16.0-1.el7.noarch
tfm-rubygem-foreman-tasks-core-0.2.0-1.fm1_16.el7.noarch
foreman-cli-1.16.0-1.el7.noarch
foreman-installer-1.16.0-1.el7.noarch
foreman-proxy-1.16.0-1.el7.noarch
[root@foreman foreman]#
foreman-installer \
--enable-foreman-plugin-chef \
--enable-foreman-plugin-tasks \
--enable-foreman-proxy-plugin-chef \
--foreman-proxy-plugin-chef-server-url="https://chefserver.j.com/organizations/my_cloud" \
--foreman-proxy-plugin-chef-client-name="jack" \
--foreman-proxy-plugin-chef-private-key="/etc/opscode/jack.pem" \
--no-enable-puppet \
--foreman-server-ssl-crl=""
And then I created a machine（"Create Host"）：
The last three items are not configured
The following error occurred when I clicked on submit
The error log is as follows
2017-12-26 19:44:45 c9697cf2 [foreman-tasks/action] [E] ERF12-0944 [ForemanChef::ProxyException]: Unab
le to communicate with Chef proxy, 500 Internal Server Error (ForemanChef::ProxyException)
| /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_chef-0.5.0/app/lib/actions/foreman_chef/host/c
reate.rb:31:in `rescue in plan'
| /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_chef-0.5.0/app/lib/actions/foreman_chef/host/c
reate.rb:11:in `plan'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/action.rb:468:in `block (3
levels) in execute_plan'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware/stack.rb:26:in `
call'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware/stack.rb:26:in `
pass'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware.rb:17:in `pass'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware.rb:34:in `plan'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware/stack.rb:22:in `
call'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware/stack.rb:26:in `
pass'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware.rb:17:in `pass'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware.rb:34:in `plan'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware/stack.rb:22:in `
call'
| /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.30/lib/dynflow/middleware/world.rb:30:in `
execute'
.........
Updated by snow snow almost 7 years ago
The problem has been solved. I re-use foreman-installer installed foreman_chef found yum foreman_chef version is 0.6.0,