The setup… the host is Satellite-6 (aka foretello). I have 'puppet agent -t' working on the host and seeing my puppet modules (I did have to add 'environmentpath = $confdir/environments' to the [main] section of puppet.conf). I see lots of reports for the host in the UI. When I push the 'Run Puppet' button (after enabling it in settings), I get the following:
failed to execute puppetrun: ERF12-4252 [ProxyAPI::ProxyException]: Unable to execute Puppet run ([RestClient::InternalServerError]: 500 Internal Server Error) for proxy https://thomasmckay-beta.usersys.redhat.com:9090/puppet
What should I be looking for to debug this? How do I configure the server to manage itself (seems like I'm very close)?
Apologies in advance, but I am looking for beginner instructions for debug and solutions. Phrases like, "Make sure the server's ssl certs are…" mean nothing to me. Something like, "Make sure /var/lib/puppet/ssl is…" will be more likely to actually help.
Thanks in advance!
···
--
@thomasmckay
–
“The leader must aim high, see big, judge widely, thus setting himself apart form the ordinary people who debate in narrow confines.” ~ Charles De Gaulle
“Leadership is about making others better as a result of your presence and making sure that impact lasts in your absence.” ~ Harvard Business School
>
> The setup… the host is Satellite-6 (aka foretello). I have 'puppet agent
> -t' working on the host and seeing my puppet modules (I did have to add
> 'environmentpath = $confdir/environments' to the [main] section of
> puppet.conf). I see lots of reports for the host in the UI. When I push the
> 'Run Puppet' button (after enabling it in settings), I get the following:
>
> failed to execute puppetrun: ERF12-4252 [ProxyAPI::ProxyException]: Unable to
> execute Puppet run ([RestClient::InternalServerError]: 500 Internal Server
> Error) for proxy https://thomasmckay-beta.usersys.redhat.com:9090/puppet
>
> What should I be looking for to debug this? How do I configure the server to
> manage itself (seems like I'm very close)?
>
> Apologies in advance, but I am looking for beginner instructions for debug
> and solutions. Phrases like, "Make sure the server's ssl certs are…" mean
> nothing to me. Something like, "Make sure /var/lib/puppet/ssl is…" will be
> more likely to actually help.
>
> Thanks in advance!
>
>
Thanks to @YamakasY on #theforeman IRC for linking me to an article[1] that outlined the steps. Beyond my own fumblings (I added listen=true to [main] but neglected to notice that it was already in [agent] as false), this got me to the final point of successfully being able to use the 'Run Puppet' button on my Satellite-6 server itself.
[1] http://wiki.infn.it/progetti/cloud-areapd/best_practices/config_puppetrun
···
----- Original Message -----
–
@thomasmckay
–
“The leader must aim high, see big, judge widely, thus setting himself apart
form the ordinary people who debate in narrow confines.” ~ Charles De Gaulle
“Leadership is about making others better as a result of your presence and
making sure that impact lasts in your absence.” ~ Harvard Business School
–
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.
Thanks! I was having the same problems… Did you change the
:puppet_provider in foreman-proxy/settings.yml ?
enable Puppet management
:puppet: true
:puppet_conf: /etc/puppet/puppet.conf
valid providers:
puppetrun (for puppetrun/kick, deprecated in Puppet 3)
mcollective (uses mco puppet)
puppetssh (run puppet over ssh)
salt (uses salt puppet.run)
customrun (calls a custom command with args)
#:puppet_provider: puppetrun
Kind regards,
Jorick Astrego
···
On 08/03/2014 04:39 PM, Tom McKay wrote:
>
> ----- Original Message -----
>> The setup... the host is Satellite-6 (aka foretello). I have 'puppet agent
>> -t' working on the host and seeing my puppet modules (I did have to add
>> 'environmentpath = $confdir/environments' to the [main] section of
>> puppet.conf). I see lots of reports for the host in the UI. When I push the
>> 'Run Puppet' button (after enabling it in settings), I get the following:
>>
>> failed to execute puppetrun: ERF12-4252 [ProxyAPI::ProxyException]: Unable to
>> execute Puppet run ([RestClient::InternalServerError]: 500 Internal Server
>> Error) for proxy https://thomasmckay-beta.usersys.redhat.com:9090/puppet
>>
>> What should I be looking for to debug this? How do I configure the server to
>> manage itself (seems like I'm very close)?
>>
>> Apologies in advance, but I am looking for beginner instructions for debug
>> and solutions. Phrases like, "Make sure the server's ssl certs are..." mean
>> nothing to me. Something like, "Make sure /var/lib/puppet/ssl is..." will be
>> more likely to actually help.
>>
>> Thanks in advance!
>>
>>
> Thanks to @YamakasY on #theforeman IRC for linking me to an article[1] that outlined the steps. Beyond my own fumblings (I added listen=true to [main] but neglected to notice that it was already in [agent] as false), this got me to the final point of successfully being able to use the 'Run Puppet' button on my Satellite-6 server itself.
>
> [1] http://wiki.infn.it/progetti/cloud-areapd/best_practices/config_puppetrun
Those settings are not in my settings.yml so no, I did not have to change anything there.
···
----- Original Message -----
>
> On 08/03/2014 04:39 PM, Tom McKay wrote:
> >
> > ----- Original Message -----
> >> The setup... the host is Satellite-6 (aka foretello). I have 'puppet agent
> >> -t' working on the host and seeing my puppet modules (I did have to add
> >> 'environmentpath = $confdir/environments' to the [main] section of
> >> puppet.conf). I see lots of reports for the host in the UI. When I push
> >> the
> >> 'Run Puppet' button (after enabling it in settings), I get the following:
> >>
> >> failed to execute puppetrun: ERF12-4252 [ProxyAPI::ProxyException]: Unable
> >> to
> >> execute Puppet run ([RestClient::InternalServerError]: 500 Internal Server
> >> Error) for proxy https://thomasmckay-beta.usersys.redhat.com:9090/puppet
> >>
> >> What should I be looking for to debug this? How do I configure the server
> >> to
> >> manage itself (seems like I'm very close)?
> >>
> >> Apologies in advance, but I am looking for beginner instructions for debug
> >> and solutions. Phrases like, "Make sure the server's ssl certs are..."
> >> mean
> >> nothing to me. Something like, "Make sure /var/lib/puppet/ssl is..." will
> >> be
> >> more likely to actually help.
> >>
> >> Thanks in advance!
> >>
> >>
> > Thanks to @YamakasY on #theforeman IRC for linking me to an article[1] that
> > outlined the steps. Beyond my own fumblings (I added listen=true to [main]
> > but neglected to notice that it was already in [agent] as false), this got
> > me to the final point of successfully being able to use the 'Run Puppet'
> > button on my Satellite-6 server itself.
> >
> > [1]
> > http://wiki.infn.it/progetti/cloud-areapd/best_practices/config_puppetrun
>
> Thanks! I was having the same problems... Did you change the
> :puppet_provider in foreman-proxy/settings.yml ?
>
> # enable Puppet management
> :puppet: true
> :puppet_conf: /etc/puppet/puppet.conf
> # valid providers:
> # puppetrun (for puppetrun/kick, *deprecated in Puppet 3*)
> # mcollective (uses mco puppet)
> # puppetssh (run puppet over ssh)
> # salt (uses salt puppet.run)
> # customrun (calls a custom command with args)
> #:puppet_provider: puppetrun
>
> Kind regards,
>
> Jorick Astrego
>
Hi Tom,
Any ideas about your problem it's solved ?
I have the same problem with my foreman.
puppetrun : ERF12-4252 [ProxyAPI::ProxyException]: Impossible d'exécuter
Puppet run ([RestClient::RequestTimeout]: Request Timeout) pour le proxy
https://localhost:8443/puppet
···
Le lundi 4 août 2014 15:15:13 UTC+2, Tom McKay a écrit :
>
>
>
> ----- Original Message -----
> >
> > On 08/03/2014 04:39 PM, Tom McKay wrote:
> > >
> > > ----- Original Message -----
> > >> The setup... the host is Satellite-6 (aka foretello). I have 'puppet
> agent
> > >> -t' working on the host and seeing my puppet modules (I did have to
> add
> > >> 'environmentpath = $confdir/environments' to the [main] section of
> > >> puppet.conf). I see lots of reports for the host in the UI. When I
> push
> > >> the
> > >> 'Run Puppet' button (after enabling it in settings), I get the
> following:
> > >>
> > >> failed to execute puppetrun: ERF12-4252 [ProxyAPI::ProxyException]:
> Unable
> > >> to
> > >> execute Puppet run ([RestClient::InternalServerError]: 500 Internal
> Server
> > >> Error) for proxy
> https://thomasmckay-beta.usersys.redhat.com:9090/puppet
> > >>
> > >> What should I be looking for to debug this? How do I configure the
> server
> > >> to
> > >> manage itself (seems like I'm very close)?
> > >>
> > >> Apologies in advance, but I am looking for beginner instructions for
> debug
> > >> and solutions. Phrases like, "Make sure the server's ssl certs
> are..."
> > >> mean
> > >> nothing to me. Something like, "Make sure /var/lib/puppet/ssl is..."
> will
> > >> be
> > >> more likely to actually help.
> > >>
> > >> Thanks in advance!
> > >>
> > >>
> > > Thanks to @YamakasY on #theforeman IRC for linking me to an article[1]
> that
> > > outlined the steps. Beyond my own fumblings (I added listen=true to
> [main]
> > > but neglected to notice that it was already in [agent] as false), this
> got
> > > me to the final point of successfully being able to use the 'Run
> Puppet'
> > > button on my Satellite-6 server itself.
> > >
> > > [1]
> > >
> http://wiki.infn.it/progetti/cloud-areapd/best_practices/config_puppetrun
> >
> > Thanks! I was having the same problems... Did you change the
> > :puppet_provider in foreman-proxy/settings.yml ?
> >
> > # enable Puppet management
> > :puppet: true
> > :puppet_conf: /etc/puppet/puppet.conf
> > # valid providers:
> > # puppetrun (for puppetrun/kick, *deprecated in Puppet 3*)
> > # mcollective (uses mco puppet)
> > # puppetssh (run puppet over ssh)
> > # salt (uses salt puppet.run)
> > # customrun (calls a custom command with args)
> > #:puppet_provider: puppetrun
> >
> > Kind regards,
> >
> > Jorick Astrego
> >
>
> Those settings are not in my settings.yml so no, I did not have to change
> anything there.
>
> Hi Tom,
>
> Any ideas about your problem it's solved ?
>
> I have the same problem with my foreman.
>
> puppetrun : ERF12-4252 [ProxyAPI::ProxyException]: Impossible d'exécuter
> Puppet run ([RestClient::RequestTimeout]: Request Timeout) pour le proxy
> https://localhost:8443/puppet
>
> >
> >
> >
> > >
> > > >
> > > >> The setup… the host is Satellite-6 (aka foretello). I have 'puppet
> > agent
> > > >> -t' working on the host and seeing my puppet modules (I did have to
> > add
> > > >> 'environmentpath = $confdir/environments' to the [main] section of
> > > >> puppet.conf). I see lots of reports for the host in the UI. When I
> > push
> > > >> the
> > > >> 'Run Puppet' button (after enabling it in settings), I get the
> > following:
> > > >>
> > > >> failed to execute puppetrun: ERF12-4252 [ProxyAPI::ProxyException]:
> > Unable
> > > >> to
> > > >> execute Puppet run ([RestClient::InternalServerError]: 500 Internal
> > Server
> > > >> Error) for proxy
> > https://thomasmckay-beta.usersys.redhat.com:9090/puppet
> > > >>
> > > >> What should I be looking for to debug this? How do I configure the
> > server
> > > >> to
> > > >> manage itself (seems like I'm very close)?
> > > >>
> > > >> Apologies in advance, but I am looking for beginner instructions for
> > debug
> > > >> and solutions. Phrases like, "Make sure the server's ssl certs
> > are…"
> > > >> mean
> > > >> nothing to me. Something like, "Make sure /var/lib/puppet/ssl is…"
> > will
> > > >> be
> > > >> more likely to actually help.
> > > >>
> > > >> Thanks in advance!
> > > >>
> > > >>
> > > > Thanks to @YamakasY on #theforeman IRC for linking me to an article[1]
> > that
> > > > outlined the steps. Beyond my own fumblings (I added listen=true to
> > [main]
> > > > but neglected to notice that it was already in [agent] as false), this
> > got
> > > > me to the final point of successfully being able to use the 'Run
> > Puppet'
> > > > button on my Satellite-6 server itself.
> > > >
> > > > [1]
> > > >
> > http://wiki.infn.it/progetti/cloud-areapd/best_practices/config_puppetrun
> > >
> > > Thanks! I was having the same problems… Did you change the
> > > :puppet_provider in foreman-proxy/settings.yml ?
> > >
> > > # enable Puppet management
> > > :puppet: true
> > > :puppet_conf: /etc/puppet/puppet.conf
> > > # valid providers:
> > > # puppetrun (for puppetrun/kick, deprecated in Puppet 3)
> > > # mcollective (uses mco puppet)
> > > # puppetssh (run puppet over ssh)
> > > # salt (uses salt puppet.run)
> > > # customrun (calls a custom command with args)
> > > #:puppet_provider: puppetrun
> > >
> > > Kind regards,
> > >
> > > Jorick Astrego
> > >
> >
> > Those settings are not in my settings.yml so no, I did not have to change
> > anything there.
> >
>
···
From my notes, the only thing that might help you is to make sure puppet.conf has listen=true in the [agent] section.
----- Original Message -----
> Le lundi 4 août 2014 15:15:13 UTC+2, Tom McKay a écrit :
> > ----- Original Message -----
> > > On 08/03/2014 04:39 PM, Tom McKay wrote:
> > > > ----- Original Message -----
