Bug #3030

Insufficiently specific error message when a fileserver module doesn't exist

Added by Jesse Wolfe over 3 years ago. Updated over 1 year ago.

Status:Re-openedStart date:01/11/2010
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Affected Puppet version:0.25.2 Branch:
Keywords:

Description

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

Related issues

Related to Puppet - Bug #4600: file server problems running under passenger Duplicate 08/24/2010

History

#1 Updated by Markus Roberts over 3 years ago

  • Status changed from Unreviewed to Accepted

#2 Updated by James Turnbull over 3 years ago

  • Target version changed from 0.25.4 to 0.25.5

#3 Updated by James Turnbull about 3 years ago

  • Target version changed from 0.25.5 to 49

#4 Updated by James Turnbull over 2 years ago

  • Target version deleted (49)

#5 Updated by Joshua Lifton over 1 year ago

  • Assignee deleted (Jesse Wolfe)

This issue was assigned to a former Puppet Labs employee. Adding back to the pool of unreviewed issues.

#6 Updated by Joshua Lifton over 1 year ago

Updating tickets assigned to a former Puppet Labs employee.

#7 Updated by Joshua Lifton over 1 year ago

  • Description updated (diff)

#8 Updated by Joshua Lifton over 1 year ago

  • Status changed from Accepted to Investigating

#9 Updated by Joshua Lifton over 1 year ago

  • Description updated (diff)
  • Status changed from Investigating to Accepted

#10 Updated by Ben Hughes over 1 year ago

  • Description updated (diff)
  • Status changed from Accepted to Unreviewed

#11 Updated by Daniel Pittman over 1 year ago

  • Description updated (diff)
  • Status changed from Unreviewed to Closed

Looks like this was fixed along the way. If not we can painfully rediscover it again later.

#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.

Also available in: Atom PDF