I'm having a weird problem - when trying to connect to my foreman-proxy on
my puppet box to import classes, I get an error. After looking further into
this, it seems that the proxy does not read my settings in my ENC script
(/etc/puppet/node.rb) correctly. These values seem to be validated
in /usr/share/foreman-proxy/lib/proxy/puppet/api_request.rb and if I edit
this file and hardcode my node.rb values there as the fallback default,
then it works. The values in question are @url, @ssl_ca, @ssl_cert and
@ssl_key. I've checked permissions on node.rb and thats fine.
Anyone recognizing this problem or have an idea what it may be?
Cheers,
Adam
> I'm having a weird problem - when trying to connect to my foreman-proxy
> on my puppet box to import classes, I get an error.
Could you share the error?
> After looking
> further into this, it seems that the proxy does not read my settings in
> my ENC script (/etc/puppet/node.rb) correctly. These values seem to be
> validated in /usr/share/foreman-proxy/lib/proxy/puppet/api_request.rb
> and if I edit this file and hardcode my node.rb values there as the
> fallback default, then it works. The values in question are @url,
> @ssl_ca, @ssl_cert and @ssl_key. I've checked permissions on node.rb and
> thats fine.
>
> Anyone recognizing this problem or have an idea what it may be?
The Proxy to Puppet API calls are used when using Puppet's directory
environments, and are controlled by :puppet_url and :puppet_ssl_*
settings in /etc/foreman-proxy/settings.yml (settings.d/puppet.yml in
Foreman 1.6). Some information on them is provided here in the 1.6 manual:
http://theforeman.org/manuals/1.6/index.html#4.3.7Puppet
It won't read node.rb settings as they're for different things.
···
On 21/08/14 07:51, AdamW wrote:
–
Dominic Cleal
Red Hat Engineering
ah, works like a charm, thanks. The reason i didnt find these settings is
that the rpm (foreman-proxy-1.5.2-1.el6.noarch) does not create a
'settings.yml.rpmnew' file on update when there is an existings
settings.yml. So all I had was my old settings.yml where these settings
does not exist. It would be a good idea I think to build the rpm so it
creates a .rpmnew version of the config file.
Thanks again!
//Adam
···
On 21 August 2014 09:43, Dominic Cleal wrote:
On 21/08/14 07:51, AdamW wrote:
I’m having a weird problem - when trying to connect to my foreman-proxy
on my puppet box to import classes, I get an error.
Could you share the error?
After looking
further into this, it seems that the proxy does not read my settings in
my ENC script (/etc/puppet/node.rb) correctly. These values seem to be
validated in /usr/share/foreman-proxy/lib/proxy/puppet/api_request.rb
and if I edit this file and hardcode my node.rb values there as the
fallback default, then it works. The values in question are @url,
@ssl_ca, @ssl_cert and @ssl_key. I’ve checked permissions on node.rb and
thats fine.
Anyone recognizing this problem or have an idea what it may be?
The Proxy to Puppet API calls are used when using Puppet’s directory
environments, and are controlled by :puppet_url and :puppet_ssl_*
settings in /etc/foreman-proxy/settings.yml (settings.d/puppet.yml in
Foreman 1.6). Some information on them is provided here in the 1.6 manual:
Foreman :: Manual
It won’t read node.rb settings as they’re for different things.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
