Hello @all,
after upgrading Foreman to 1.5, importing of Puppet classes is failing:
ProxyAPI::ProxyException
ERF12-4115 [ProxyAPI::ProxyException]: Unable to get classes from Puppet
for example_env ([RestClient::NotAcceptable]: 406 Not Acceptable) for proxy
https://manage5.ham.cimt.de:8443/puppet
<https://manage5.ham.cimt.de:8443/puppet>
lib/proxy_api/puppet.rb:27:in rescue in classes' lib/proxy_api/puppet.rb:21:inclasses'
app/services/puppet_class_importer.rb:155:in actual_classes' app/services/puppet_class_importer.rb:78:innew_classes_for'
app/services/puppet_class_importer.rb:25:in block in changes' app/services/puppet_class_importer.rb:24:ineach'
app/services/puppet_class_importer.rb:24:in changes' app/controllers/concerns/foreman/controller/environments.rb:11:inimport_environments'
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall'
Any hints? The example_env directory is provided by the puppet-server RPM
and deleting it don't solve the problem:
ProxyAPI::ProxyException
ERF12-4115 [ProxyAPI::ProxyException]: Unable to get classes from Puppet
for production ([RestClient::NotAcceptable]: 406 Not Acceptable) for proxy
https://manage5.ham.cimt.de:8443/puppet
<https://manage5.ham.cimt.de:8443/puppet>
lib/proxy_api/puppet.rb:27:in rescue in classes' lib/proxy_api/puppet.rb:21:inclasses'
app/services/puppet_class_importer.rb:155:in actual_classes' app/services/puppet_class_importer.rb:78:innew_classes_for'
app/services/puppet_class_importer.rb:25:in block in changes' app/services/puppet_class_importer.rb:24:ineach'
app/services/puppet_class_importer.rb:24:in changes' app/controllers/concerns/foreman/controller/environments.rb:11:inimport_environments'
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall'
It complain now the production environment which is of course working.
Regards Thomas
···
--
Linux ... enjoy the ride!
You mention "The example_env directory" - does this imply you're using
the new directory environments feature of Puppet 3.5+ ? if so, be
aware the proxy doesn't yet support it.
Yes, that't true, I switched to dynamic environments to clean up the
configuration. Do you know when it is planned to support dynamic
environments with foreman proxy?
Regards, Thomas
···
2014-05-23 12:00 GMT+02:00 Greg Sutcliffe :
You mention “The example_env directory” - does this imply you’re using
the new directory environments feature of Puppet 3.5+ ? if so, be
aware the proxy doesn’t yet support it.
–
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.
–
performance, security, automation, SAP
cimt consulting ag, Burchardstrasse 17, 20095 Hamburg
fon: +49 (163) 6081 302, fax: +49 (40) 5 33 02-22, web: www.cimt.de
key: FED7C867 at pgp.mit.edu
Sitz der Gesellschaft: Hamburg, Amtsgericht Hamburg, HRB 74173
Vorstand: Christoph Friedlaender, Dr.-Ing. Thorsten Kuhlmann
Vorsitzender des Aufsichtsrats: Christian Gottsmann
I have the same error as well. It looks like the issue is marked as
"urgent" in the tracker, so I suppose the solution will come asap.
http://projects.theforeman.org/issues/5856
···
El viernes, 23 de mayo de 2014 12:26:55 UTC+2, Thomas Bendler escribió:
>
> Yes, that't true, I switched to dynamic environments to clean up the
> configuration. Do you know when it is planned to support dynamic
> environments with foreman proxy?
>
> Regards, Thomas
>
>
> 2014-05-23 12:00 GMT+02:00 Greg Sutcliffe <greg.su...@gmail.com
> >:
>
>> You mention "The example_env directory" - does this imply you're using
>> the new directory environments feature of Puppet 3.5+ ? if so, be
>> aware the proxy doesn't yet support it.
>>
>> --
>> 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-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> performance, security, automation, SAP
> cimt consulting ag, Burchardstrasse 17, 20095 Hamburg
> fon: +49 (163) 6081 302, fax: +49 (40) 5 33 02-22, web: www.cimt.de
> key: FED7C867 at pgp.mit.edu
>
> Sitz der Gesellschaft: Hamburg, Amtsgericht Hamburg, HRB 74173
> Vorstand: Christoph Friedlaender, Dr.-Ing. Thorsten Kuhlmann
> Vorsitzender des Aufsichtsrats: Christian Gottsmann
>
I also hitted the error with puppet 3.6.1 and this puppet.conf
Downgrading to 3.5.1 brought me back to work
File managed with puppet
Module: 'puppet'
[main]
# The Puppet log directory.
# The default value is '$vardir/log'.
logdir = /var/log/puppet
# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
rundir = /var/run/puppet
# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = $vardir/ssl
# Allow services in the 'puppet' group to access key (Foreman + proxy)
privatekeydir = $ssldir/private_keys { group = service }
hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
# Puppet 3.0.x requires this in both [main] and [master] - harmless on
agents
autosign = $confdir/autosign.conf { mode = 664 }
show_diff = false
environmentpath = $confdir/environments
Next part of the file is managed by a different template
Module: 'puppet'
[agent]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate puppet executable using the --loadclasses
# option.
# The default value is '$statedir/classes.txt'.
classfile = $vardir/classes.txt
# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig
# Disable the default schedules as they cause continual skipped
# resources to be displayed in Foreman - only for Puppet >= 3.4
default_schedules = false
report = true
pluginsync = true
masterport = 8140
environment = cloudbox
certname = server.local.cloud
server = server.local.cloud
listen = false
splay = false
runinterval = 1800
noop = false
configtimeout = 120
Next part of the file is managed by a different template
Module: 'puppet'
[master]
autosign = $confdir/autosign.conf { mode = 664 }
reports = foreman
external_nodes = /etc/puppet/node.rb
node_terminus = exec
ca = true
ssldir = /var/lib/puppet/ssl
certname = server.local.cloud
strict_variables = false
[cloudbox]
modulepath =
/etc/puppet/environments/cloudbox/modules:/etc/puppet/environments/common:/usr/share/puppet/modules
config_version =
···
Am Freitag, 23. Mai 2014 13:00:32 UTC+2 schrieb Dominic Cleal:
>
> On 23/05/14 11:45, Félix Barbeira wrote:
> > I have the same error as well. It looks like the issue is marked as
> > "urgent" in the tracker, so I suppose the solution will come asap.
> >
> > http://projects.theforeman.org/issues/5856
>
> Please note that there are two distinct things here:
>
> 1. Directory environments are unsupported in the smart proxy today,
> which is what Thomas appears to have hit. I'd like to do this soon, but
> not for 1.5.1. That's tracked in
> http://projects.theforeman.org/issues/4699.
>
> 2. There are some strange issues with Puppet 3.6.x in certain
> environment configurations which are throwing environment-related
> errors, which is what I'm tracking in #5856 and investigating at the
> moment.
>
> There are reports of similar errors on #puppet of Puppet itself throwing
> the same error in some circumstances, so am beginning to suspect the
> issue may in part be there.
>
> I'd appreciate copies of puppet.conf attached to the bug report from
> anybody hitting the error in #5856 and who aren't using directory
> environments (Felix?). Thanks!
>
> --
> Dominic Cleal
> Red Hat Engineering
>
I think I'm more related with the second case.
root@server:~# puppet -V
3.6.1
root@server:~#
Trying to import the environments/classes the smart-proxy throws the
following error:
E, [2014-05-23T12:35:19.149408 #1411] ERROR – : Failed to show puppet
classes: no 'environments' in
{:current_environment=>#<Puppet::Node::Environment:0x7f64a1775210
@config_version=nil, @name=:"root", @manifest="/", @modulepath=[],
@watching=true>,
:root_environment=>#<Puppet::Node::Environment:0x7f64a1775210
@config_version=nil, @name=:"root", @manifest="/", @modulepath=[],
@watching=true>} at top of [[0, nil, nil]]
Foreman web interface:
ProxyAPI::ProxyException
ERF12-4115 [ProxyAPI::ProxyException]: Unable to get classes from Puppet
for develop ([RestClient::NotAcceptable]: 406 Not Acceptable) for proxy
https://server:8443/puppet
lib/proxy_api/puppet.rb:27:in rescue in classes' lib/proxy_api/puppet.rb:21:inclasses'
app/services/puppet_class_importer.rb:155:in actual_classes' app/services/puppet_class_importer.rb:78:innew_classes_for'
app/services/puppet_class_importer.rb:25:in block in changes' app/services/puppet_class_importer.rb:24:ineach'
app/services/puppet_class_importer.rb:24:in changes' app/controllers/concerns/foreman/controller/environments.rb:11:inimport_environments'
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall'
And finally this is my puppet.conf file:
[main]
logdir = /var/log/puppet
vardir = /var/lib/puppet
ssldir = $vardir/ssl
rundir = /var/run/puppet
factpath = $vardir/lib/facter
confdir = /etc/puppet
templatedir = $confdir/templates
hiera_config = $confdir/hiera.yaml
[master]
These are needed when the puppetmaster is run by passenger
and can safely be removed if webrick is used.
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
reports = foreman,puppetdb,tagmail
autosign = $confdir/autosign.conf
node_terminus = exec
external_nodes = $confdir/node.rb
storeconfigs = true
storeconfigs_backend = puppetdb
#environmentpath = $confdir/environments
manifest = $confdir/environments/$environment/manifests/site.pp
modulepath = $confdir/environments/$environment/modules
[agent]
report = true
I hope it helps with the issue.
···
El viernes, 23 de mayo de 2014 13:00:32 UTC+2, Dominic Cleal escribió:
>
> On 23/05/14 11:45, Félix Barbeira wrote:
> > I have the same error as well. It looks like the issue is marked as
> > "urgent" in the tracker, so I suppose the solution will come asap.
> >
> > http://projects.theforeman.org/issues/5856
>
> Please note that there are two distinct things here:
>
> 1. Directory environments are unsupported in the smart proxy today,
> which is what Thomas appears to have hit. I'd like to do this soon, but
> not for 1.5.1. That's tracked in
> http://projects.theforeman.org/issues/4699.
>
> 2. There are some strange issues with Puppet 3.6.x in certain
> environment configurations which are throwing environment-related
> errors, which is what I'm tracking in #5856 and investigating at the
> moment.
>
> There are reports of similar errors on #puppet of Puppet itself throwing
> the same error in some circumstances, so am beginning to suspect the
> issue may in part be there.
>
> I'd appreciate copies of puppet.conf attached to the bug report from
> anybody hitting the error in #5856 and who aren't using directory
> environments (Felix?). Thanks!
>
> --
> Dominic Cleal
> Red Hat Engineering
>
Please note that there are two distinct things here:
-
Directory environments are unsupported in the smart proxy today,
which is what Thomas appears to have hit. I'd like to do this soon, but
not for 1.5.1. That's tracked in
Feature #4699: Support Puppet environmentpath and environment config files - Smart Proxy - Foreman.
-
There are some strange issues with Puppet 3.6.x in certain
environment configurations which are throwing environment-related
errors, which is what I'm tracking in #5856 and investigating at the moment.
There are reports of similar errors on #puppet of Puppet itself throwing
the same error in some circumstances, so am beginning to suspect the
issue may in part be there.
I'd appreciate copies of puppet.conf attached to the bug report from
anybody hitting the error in #5856 and who aren't using directory
environments (Felix?). Thanks!
···
On 23/05/14 11:45, Félix Barbeira wrote:
> I have the same error as well. It looks like the issue is marked as
> "urgent" in the tracker, so I suppose the solution will come asap.
>
> http://projects.theforeman.org/issues/5856
–
Dominic Cleal
Red Hat Engineering
Thanks to both Felixes!
I've put a patch up for review, you can apply and test it with:
cd /usr/share/foreman-proxy && curl
https://github.com/theforeman/smart-proxy/pull/161.patch | patch -p1
···
On 23/05/14 12:23, Felix Massem wrote:
> I also hitted the error with puppet 3.6.1 and this puppet.conf
>
> Downgrading to 3.5.1 brought me back to work
–
Dominic Cleal
Red Hat Engineering
Thanks Dominic,
I had the same issue and was trying a different work-around.
Using your patch and restarting the foreman-proxy service worked fine.
Regards,
P.
···
On Friday, May 23, 2014 4:00:22 PM UTC+3, Dominic Cleal wrote:
>
> On 23/05/14 12:23, Felix Massem wrote:
> > I also hitted the error with puppet 3.6.1 and this puppet.conf
> >
> > Downgrading to 3.5.1 brought me back to work
>
> Thanks to both Felixes!
>
> I've put a patch up for review, you can apply and test it with:
>
> cd /usr/share/foreman-proxy && curl
> https://github.com/theforeman/smart-proxy/pull/161.patch | patch -p1
>
> --
> Dominic Cleal
> Red Hat Engineering
>
I installed the patch, and while it seemed to work, the only thing it wants
to do now is remove all my environments and the classes from them when I
try to import new classes. I'm using the old directory environments, but
have updated the config file for 3.6.1
[main]
# The Puppet log directory.
# The default value is '$vardir/log'.
logdir = /var/log/puppet
# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
rundir = /var/run/puppet
# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = $vardir/ssl
privatekeydir = $ssldir/private_keys { group = service }
hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
[agent]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate puppet executable using the --loadclasses
# option.
# The default value is '$confdir/classes.txt'.
classfile = $vardir/classes.txt
# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig
report = true
[master]
basemodulepath = $confdir/modules
storeconfigs = true
storeconfigs_backend = puppetdb
ca = true
reports = log,foreman
external_nodes = /etc/puppet/node.rb
node_terminus = exec
autosign = true
environmentpath = $confdir/environments
···
On Friday, May 23, 2014 9:00:22 AM UTC-4, Dominic Cleal wrote:
>
> On 23/05/14 12:23, Felix Massem wrote:
> > I also hitted the error with puppet 3.6.1 and this puppet.conf
> >
> > Downgrading to 3.5.1 brought me back to work
>
> Thanks to both Felixes!
>
> I've put a patch up for review, you can apply and test it with:
>
> cd /usr/share/foreman-proxy && curl
> https://github.com/theforeman/smart-proxy/pull/161.patch | patch -p1
>
> --
> Dominic Cleal
> Red Hat Engineering
>
On Friday, May 23, 2014 9:00:22 AM UTC-4, Dominic Cleal wrote:
On 23/05/14 12:23, Felix Massem wrote:
I also hitted the error with puppet 3.6.1 and this puppet.conf
Downgrading to 3.5.1 brought me back to work
Thanks to both Felixes!
I’ve put a patch up for review, you can apply and test it with:
cd /usr/share/foreman-proxy && curl
https://github.com/theforeman/smart-proxy/pull/161.patch | patch -p1
–
Dominic Cleal
Red Hat Engineering
It also solved my problem, thanks for the patch!
Regards Thomas
···
2014-05-26 11:01 GMT+02:00 Félix Barbeira :
It worked! 
El viernes, 23 de mayo de 2014 15:00:22 UTC+2, Dominic Cleal escribió:
On 23/05/14 12:23, Felix Massem wrote:
I also hitted the error with puppet 3.6.1 and this puppet.conf
Downgrading to 3.5.1 brought me back to work
Thanks to both Felixes!
I’ve put a patch up for review, you can apply and test it with:
cd /usr/share/foreman-proxy && curl
https://github.com/theforeman/smart-proxy/pull/161.patch | patch -p1
–
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.
–
Linux … enjoy the ride!
Directory environments aren't currently supported (watch
Feature #4699: Support Puppet environmentpath and environment config files - Smart Proxy - Foreman), you should use the older
non-directory (non-environmentpath) style:
http://docs.puppetlabs.com/guides/environment.html#configuring-environments-on-the-puppet-master
···
--
Dominic Cleal
Red Hat Engineering
On 11/06/14 15:14, Andrew Hamilton wrote:
I installed the patch, and while it seemed to work, the only thing it
wants to do now is remove all my environments and the classes from them
when I try to import new classes. I’m using the old directory
environments, but have updated the config file for 3.6.1
[main]
# The Puppet log directory.
# The default value is ‘$vardir/log’.
logdir = /var/log/puppet
# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
rundir = /var/run/puppet
# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = $vardir/ssl
privatekeydir = $ssldir/private_keys { group = service }
hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
[agent]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate puppet executable using the --loadclasses
# option.
# The default value is ‘$confdir/classes.txt’.
classfile = $vardir/classes.txt
# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig
report = true
[master]
basemodulepath = $confdir/modules
storeconfigs = true
storeconfigs_backend = puppetdb
ca = true
reports = log,foreman
external_nodes = /etc/puppet/node.rb
node_terminus = exec
autosign = true
environmentpath = $confdir/environments
On Friday, May 23, 2014 9:00:22 AM UTC-4, Dominic Cleal wrote:
On 23/05/14 12:23, Felix Massem wrote:
> I also hitted the error with puppet 3.6.1 and this puppet.conf
>
> Downgrading to 3.5.1 brought me back to work
Thanks to both Felixes!
I've put a patch up for review, you can apply and test it with:
cd /usr/share/foreman-proxy && curl
https://github.com/theforeman/smart-proxy/pull/161.patch
<https://github.com/theforeman/smart-proxy/pull/161.patch> | patch -p1
--
Dominic Cleal
Red Hat Engineering
On Friday, May 23, 2014 9:00:22 AM UTC-4, Dominic Cleal wrote:
On 23/05/14 12:23, Felix Massem wrote:
> I also hitted the error with puppet 3.6.1 and this puppet.conf
>
> Downgrading to 3.5.1 brought me back to work
Thanks to both Felixes!
I've put a patch up for review, you can apply and test it with:
cd /usr/share/foreman-proxy && curl
https://github.com/theforeman/smart-proxy/pull/161.patch
<https://github.com/theforeman/smart-proxy/pull/161.patch> | patch -p1
--
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
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto: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.
Thank you! As a first time user who had issues getting set up with my
existing puppet env, this confused me to all end but you'd already resolved
it!
···
On Monday, May 26, 2014 4:42:41 AM UTC-5, thbe wrote:
>
> It also solved my problem, thanks for the patch!
>
> Regards Thomas
>
>
> 2014-05-26 11:01 GMT+02:00 Félix Barbeira <fbar...@gmail.com
> >:
>
>> It worked! :)
>>
>> El viernes, 23 de mayo de 2014 15:00:22 UTC+2, Dominic Cleal escribió:
>>
>>> On 23/05/14 12:23, Felix Massem wrote:
>>> > I also hitted the error with puppet 3.6.1 and this puppet.conf
>>> >
>>> > Downgrading to 3.5.1 brought me back to work
>>>
>>> Thanks to both Felixes!
>>>
>>> I've put a patch up for review, you can apply and test it with:
>>>
>>> cd /usr/share/foreman-proxy && curl
>>> https://github.com/theforeman/smart-proxy/pull/161.patch | patch -p1
>>>
>>> --
>>> 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-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Linux ... enjoy the ride!
>
I see. Reverting just the config file fixed it. I didn't quite get that
part from the thread.
Thanks.
···
On Wednesday, June 11, 2014 3:17:12 PM UTC-4, Dominic Cleal wrote:
>
> Directory environments aren't currently supported (watch
> http://projects.theforeman.org/issues/4699), you should use the older
> non-directory (non-environmentpath) style:
>
>
> http://docs.puppetlabs.com/guides/environment.html#configuring-environments-on-the-puppet-master
>
> --
> Dominic Cleal
> Red Hat Engineering
>
> On 11/06/14 15:14, Andrew Hamilton wrote:
> > I installed the patch, and while it seemed to work, the only thing it
> > wants to do now is remove all my environments and the classes from them
> > when I try to import new classes. I'm using the old directory
> > environments, but have updated the config file for 3.6.1
> >
> > [main]
> > # The Puppet log directory.
> > # The default value is '$vardir/log'.
> > logdir = /var/log/puppet
> >
> > # Where Puppet PID files are kept.
> > # The default value is '$vardir/run'.
> > rundir = /var/run/puppet
> >
> > # Where SSL certificates are kept.
> > # The default value is '$confdir/ssl'.
> > ssldir = $vardir/ssl
> > privatekeydir = $ssldir/private_keys { group = service }
> > hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
> >
> > [agent]
> > # The file in which puppetd stores a list of the classes
> > # associated with the retrieved configuratiion. Can be loaded in
> > # the separate ``puppet`` executable using the ``--loadclasses``
> > # option.
> > # The default value is '$confdir/classes.txt'.
> > classfile = $vardir/classes.txt
> >
> > # Where puppetd caches the local configuration. An
> > # extension indicating the cache format is added automatically.
> > # The default value is '$confdir/localconfig'.
> > localconfig = $vardir/localconfig
> > report = true
> > [master]
> > basemodulepath = $confdir/modules
> > storeconfigs = true
> > storeconfigs_backend = puppetdb
> > ca = true
> > reports = log,foreman
> > external_nodes = /etc/puppet/node.rb
> > node_terminus = exec
> > autosign = true
> > environmentpath = $confdir/environments
> >
> >
> > On Friday, May 23, 2014 9:00:22 AM UTC-4, Dominic Cleal wrote:
> >
> > On 23/05/14 12:23, Felix Massem wrote:
> > > I also hitted the error with puppet 3.6.1 and this puppet.conf
> > >
> > > Downgrading to 3.5.1 brought me back to work
> >
> > Thanks to both Felixes!
> >
> > I've put a patch up for review, you can apply and test it with:
> >
> > cd /usr/share/foreman-proxy && curl
> > https://github.com/theforeman/smart-proxy/pull/161.patch
> > | patch
> -p1
> >
> > --
> > Dominic Cleal
> > Red Hat Engineering
> >
> >
> > On Friday, May 23, 2014 9:00:22 AM UTC-4, Dominic Cleal wrote:
> >
> > On 23/05/14 12:23, Felix Massem wrote:
> > > I also hitted the error with puppet 3.6.1 and this puppet.conf
> > >
> > > Downgrading to 3.5.1 brought me back to work
> >
> > Thanks to both Felixes!
> >
> > I've put a patch up for review, you can apply and test it with:
> >
> > cd /usr/share/foreman-proxy && curl
> > https://github.com/theforeman/smart-proxy/pull/161.patch
> > | patch
> -p1
> >
> > --
> > 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-user...@googlegroups.com
> > <mailto:foreman-users+unsubscribe@googlegroups.com >.
> > To post to this group, send email to forema...@googlegroups.com
>
> > <mailto:forema...@googlegroups.com >.
> > Visit this group at http://groups.google.com/group/foreman-users.
> > For more options, visit https://groups.google.com/d/optout.
>
>
