Silly puppet misconfiguration

2009-04-15 #puppet #configuration #sysadmin

If you get an error like this:

Mar 23 16:26:08 quesadilla puppetmasterd[25945]: Denying authenticated client quesadilla.xxx(xxx) access to puppetbucket.addfile
Mar 23 16:26:08 quesadilla puppetd[32000]: Could not call puppetbucket.addfile: <RuntimeError: HTTP-Error: 500 Internal Server Error>
Mar 23 16:26:08 quesadilla puppetd[32000]: (//Node[basenode]/puppethacks/File[/etc/puppet/namespaceauth.conf]/source) change from {md5}b17c68bda4c44e7b818acb50553d0169 to puppet:///puppethacks/namespaceauth.conf failed: HTTP-Error: 500 Internal Server Error

on the server side, or like this:

Mar 23 16:24:48 crumbs puppetd[20054]: Could not call puppetbucket.addfile: <RuntimeError: HTTP-Error: 500 Internal Server Error>
Mar 23 16:24:48 crumbs puppetd[20054]: (//Node[crumbs.xxx]/dns/File[/etc/bind/named.conf.acls]/source) change from {md5}504a05051a6db6f517010ddf6b345271 to puppet:///dns/named.conf.acls failed: HTTP-Error: 500 Internal Server Error

on the client side, it is because you have a namespaceauth.conf, but didn’t allow access to the filebucket for your clients (more details).