We have a Puppet config that stores files outside of modules, along with appropriate auth.conf entries to support this. For the most part, it has just worked and I haven't felt any need to muddle with it - so I was surprised to find a bevy of these errors in the logs:
Mar 11 18:24:51 central puppet-agent[10505]: (/Stage[main]/Resolv-conf-prod/File[/etc/resolv.conf]) Could not evaluate: Could not retrieve file metadata for puppet:///files/etc/resolv.conf.prod: Error 403 on SERVER: Forbidden request: central(10.101.0.9) access to /file_metadata/files/etc/resolv.conf.prod [find] at : 128 ( hundreds of those, including /catalog ) the auth.conf entry for file_metadata says: path ~ ^/file_(metadata|content)/etc/ auth yes allow /^(.+\.)?ourdomain.com$/ allow_ip 127.0.0.0/8 allow_ip 10.0.0.0/8 That pretty much covers all. Puppet is now at 3.7.4 and it's running under Passenger, which it has been for a long time. I'm trying to figure out what's changed so I can fix this; hopefully without having to spend time writing modules that I will never use. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/592e2ac6-f714-4312-af53-ea082377610a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
