Insufficiently specific error message when a fileserver module doesn't exist
|Affected Puppet version:||0.25.2||Branch:|
As seen in the debugging for #2803 , the error message for missing fileserver content is not distinct from other types of failures, and misleads people during debugging:
Error 400 on SERVER: Not authorized to call find on /file_metadata/network-config/hosts/hosts.devcentos5
#12 Updated by Andrew Ring over 1 year ago
- Status changed from Closed to Re-opened
I am sorry, but this is still an issue.
I am running puppet agent and master version 2.6.2-5+squeeze4.
Current Non-enlightening Error:
$ sudo puppet agent —test —noop
info: Caching catalog for systemnamehere
err: Could not run Puppet configuration client: Error 400 on SERVER: Not authorized to call find on /file_metadata/files/vim/vimrc Could not retrieve file metadata for puppet://puppetmasternamehere/files/vim/vimrc: Error 400 on SERVER: Not authorized to call find on /file_metadata/files/vim/vimrc at /etc/puppet/manifests/Stable/vim.pp:19
The solution was to restart the puppetmaster daemon, but it was not apparent from the error that the issue could have been the daemon and not the script.