> I'm presuming the proxy tried to execute "puppetca list" instead of "puppet
> ca list"
>
> How do I coerce the proxy to use "puppet ca" instead of "puppetca"?
Hey,
you don't need to configure this, foreman-proxy does detect this for
you.
modules/puppetca/puppetca_main.rb#find_puppetca
Might be a bug or something, see the code and investigate why it fails
for you.
Turns out it was how the SysAdmin folks set up sudo that got in the way. I
set foreman-proxy logging to debug and watched what it was trying to do.
When I saw the "sudo" in the log files I knew where the problem was.
Thanks for pushing me in the right direction. Another entry into my
Deployment Guide for putting Foreman into production.
···
On Wed, Feb 4, 2015 at 11:45 AM, Lukas Zapletal wrote:
I’m presuming the proxy tried to execute “puppetca list” instead of
“puppet
ca list”
How do I coerce the proxy to use “puppet ca” instead of “puppetca”?
Hey,
you don’t need to configure this, foreman-proxy does detect this for
you.
modules/puppetca/puppetca_main.rb#find_puppetca
Might be a bug or something, see the code and investigate why it fails
for you.
