Activity
From 09/25/2012 to 10/24/2012
10/24/2012
- 09:36 AM Revision 6c458743: Fixes #1914: Raise if we cannot read the puppet conf file, report the path otherwise
- 09:21 AM Bug #1915 (Closed): Proxy with puppet3 causes global load errors
- If you curl the environment api call more than once, you get this:
root@installer:~# curl http://localhost:8445/pup... - 07:48 AM Bug #1914 (Closed): Proxy should throw an error when loading a nonexistant puppet.conf
- This just came up as a user upgraded from 0.4.2 to 1.0.1 - no :puppet_conf: setting in proxy/settings.yml. So the pro...
10/17/2012
- 07:44 PM Bug #1655: Failed to list puppet environments: Attempting to initialize global default settings more than once!
- This is still an issue for me as of foreman-proxy from git. Running Puppet 3.0 so it is definitely related.
10/04/2012
- 06:10 AM Bug #1885 (Resolved): user: "foreman-proxy" is unable to read inventory.txt
- 06:09 AM Bug #1885: user: "foreman-proxy" is unable to read inventory.txt
- That worked!
Thank you! - 05:59 AM Bug #1885: user: "foreman-proxy" is unable to read inventory.txt
- Can you try making it owned by puppet:puppet? The foreman-proxy should be a member of the puppet group, will then be ...
- 05:57 AM Bug #1885 (Resolved): user: "foreman-proxy" is unable to read inventory.txt
- I have installed a smart-proxy to manage PuppetCa.
The foreman-user is able to do sudo puppetca and list certificate...
Also available in: Atom