Bug #2967

clients are unable to retrieve file metadata

Added by Peter Meier 7 months ago. Updated 3 months ago.

Status:Closed Start:12/19/2009
Priority:High Due date:
Assigned to:Peter Meier % Done:

0%
Category:fileserving
Target version:0.25.2
Affected version:0.25.1 Branch:http://github.com/MarkusQ/puppet/tree/ticket/0.25.x/2967
Keywords:
Votes: 0

Description

I recently upgraded from a 3-4 weeks old 0.25.x HEAD version to latest 0.25.x head to test #2823, however file serving doesn’t work anymore completely:

Server:

debug: Using cached node for foobar.example.com, good until Sat Dec 19 19:18:34 +0100 2009
debug: Saved catalog to database in 3.28 seconds
info: mount[modules]: defaulting to no access for foobar.example.com
err: Not authorized to call search on /file_metadata/modules/yum/CentOS.5.4/rpm-gpg with {:ignore=>[".svn", ".git", "CVS", ".git_placeholder"], :recurse=>true, :links=>"manage"}
[...]

Client (different snippet):

[...]
err: //avahi::base/File[/etc/init.d/avahi-daemon]: Failed to retrieve current state of resource: Error 400 on SERVER: Not authorized to call find on /file_metadata/modules/avahi/init.d/CentOS/avahi-daemon Could not retrieve file metadata for puppet:///modules/avahi/init.d/CentOS/avahi-daemon: Error 400 on SERVER: Not authorized to call find on /file_metadata/modules/avahi/init.d/CentOS/avahi-daemon at /etc/puppet/modules/public/avahi/manifests/init.pp:27
[...]

My fileserver.conf looks like:

[modules]
  allow 127.0.0.1
  allow *.example.com
  allow *.2nd.example.com

No auth.conf is deployed.

Attached a complete —debug output of the server while one client connecting to it.

This used work with my former 0.25.x-HEAD version, so it is something that have been changed withing the last 3-4 weeks.

output.txt - output ofmaster (93.6 KB) Peter Meier, 12/19/2009 06:19 pm

History

Updated by Peter Meier 7 months ago

  • File deleted (output.txt)

Updated by Peter Meier 7 months ago

Updated by Peter Meier 7 months ago

I have been on commit:“c1e47a43df40abd5da04bf147df17f0b53bf0868”

Updated by Peter Meier 7 months ago

And I’m now on: commit:“b86decc0ea274eb6d9ffa3170fd4ec81d735519f”

Updated by Markus Roberts 7 months ago

  • Status changed from Unreviewed to Investigating
  • Target version set to 0.25.2

Updated by James Turnbull 7 months ago

  • Category set to fileserving
  • Priority changed from Normal to High

Updated by Markus Roberts 7 months ago

  • Assigned to set to Markus Roberts

Updated by Markus Roberts 7 months ago

  • Branch set to http://github.com/MarkusQ/puppet/tree/ticket/0.25.x/2967

When I try this I get:

Could not run: Invalid pattern *.2nd.example.com at ~/projects/puppet/test_data/2967m/fileserver.conf:4

which is due to our incomplete RFC-1123 compliance (we weren’t always permitting labels to start with digits).

I’m suspecting that this may be the source of the problem, or at least a confounding factor. Could you retest with the branch:

http://github.com/MarkusQ/puppet/tree/ticket/0.25.x/2967

(wherein this is fixed) with a —trace —debug —no-daemonize on the puppetmaster?

Updated by Markus Roberts 7 months ago

  • Status changed from Investigating to Needs more information
  • Assigned to changed from Markus Roberts to Peter Meier

Updated by Peter Meier 7 months ago

When I try this I get:

Could not run: Invalid pattern *.2nd.example.com at ~/projects/puppet/test_data/2967m/fileserver.conf:4

which is due to our incomplete RFC-1123 compliance (we weren’t always permitting labels to start with digits).

this wasn’t a real label more an example, but it also doesn’t work without it.

I’m suspecting that this may be the source of the problem, or at least a confounding factor. Could you retest with the branch:

http://github.com/MarkusQ/puppet/tree/ticket/0.25.x/2967

(wherein this is fixed) with a —trace —debug —no-daemonize on the puppetmaster?

I do it and report back

Updated by Peter Meier 7 months ago

I do it and report back

sent by mail to Markus.

Updated by Markus Roberts 7 months ago

  • Status changed from Needs more information to Ready for Testing

Branch updated.

Peter has privately confirmed that this worked for him.

Updated by Markus Roberts 7 months ago

  • Status changed from Ready for Testing to Ready for Checkin

It’s been +1’d and tested in the field.

Updated by James Turnbull 7 months ago

  • Status changed from Ready for Checkin to Closed

Pushed in commit:“d60ea0e52debf03fddb2336704df10589108fe3a” in branch 0.25.x and commit:“b6b33802b801c71fc7d273c172bf55362c58a1a7” also in 0.25.x

Also available in: Atom PDF