Support #22872
closedChef integration not work
Description
Perform a clean installation on a CentOS Linux release 7.4.1708 (Core).
- Foreman 1.16
- Katello 3.5
- chef-foreman 0.6
The following steps were performed for the installation:
yum -and localinstall https://fedorapeople.org/groups/katello/releases/yum/3.5/katello/el7/x86_64/katello-repos-latest.rpm
yum -y localinstall https://yum.theforeman.org/releases/1.16/el7/x86_64/foreman-release.rpm
yum -y localinstall https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
yum -and localinstall https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
yum -y install foreman-release-scl python-django
yum -y install katello
foreman-installer - katello scenario \
--enable-foreman-plugin-chef \
--enable-foreman-plugin-tasks \
--enable-foreman-proxy-plugin-chef \
--foreman-proxy-plugin-chef-server-url = "https://ljchefserver01.domain.com.ar/organizations/lojack" \
--foreman-proxy-plugin-chef-client-name = "ljforeman01.domain.com.ar" \
--foreman-proxy-plugin-chef-private-key = "/ etc / chef / client.pem" \
--foreman-proxy-plugin-chef-ssl-verify = false \
--no-enable-puppet \
--foreman-server-ssl-crl = ""
The installation finishes without errors, but when performing the tests I can import without problems the environments, attached image
But when you want to edit the smart proxy, the following error occurs:
And in Global Parameters I do not have any variable.
If I run a chef-client with the chef-handler-foreman configuration, it does not add the node.
I enclose the Full-trace of the error when editing the smart proxy and a foreman debug.
Best Regards
Files
Updated by Lucas Mariani over 6 years ago
- Status changed from New to Resolved
- Assignee set to Lucas Mariani
I was able to solve the problem.
The error when editing the smart_proxy, is that until it reports a node generates that error.
In order for the foreman handler to report the port in all in one installation, it is necessary to use port 9090 and not 8443, which is used by tomcat. Confusion was generated because the handler did not fail, since the tomcat was listening at port 8443.