Bug #994

pluginsync is broken with 'allow *' vs. 'allow *.domain.tld' specified in fileserver mount

Added by AJ Christensen over 2 years ago. Updated over 2 years ago.

Status:Closed Start:
Priority:Normal Due date:
Assignee:Puppet Community % Done:

0%
Category:-
Target version:-
Affected version:0.25.4 Branch:
Keywords:
Votes: 0

Description

Versions 0.24.1 across the board. Can’t get pluginsync running. With pluginsync=true on clients:

[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
pidfile=/var/run/puppet/puppetd.pid

[puppetd]
runinterval=120
report=true
pluginsync=true

and a fileserver mount like so:

[files]
path /etc/puppet/files
allow *

[modules]
allow *

[plugins]
allow *

puppetd —test —debug:

info: Retrieving plugins
debug: Calling fileserver.list
err: /File[/var/lib/puppet/lib]: Failed to generate additional resources during transaction: Cannot access mount[plugins]
debug: /File[/var/lib/puppet/lib]/checksum: Initializing checksum hash
debug: /File[/var/lib/puppet/lib]: Creating checksum {time}Wed Jan 09 10:28:59 +1300 2008
debug: Calling fileserver.describe
err: /File[/var/lib/puppet/lib]/source: Could not describe /plugins: Cannot access mount[plugins]
info: /File[/var/lib/puppet/lib]/source: No specified sources exist
debug: Finishing transaction -611388618 with 0 changes

puppetmasterd —verbose —no-daemonize

info: Starting server for Puppet version 0.24.1
info: mount[files]: allowing * access
info: mount[modules]: allowing * access
info: mount[plugins]: allowing * access
info: Listening on port 8140
notice: Starting Puppet server version 0.24.1
info: mount[plugins]: defaulting to no access for asterisk01.maxnet.net.nz
warning: mount[plugins]: asterisk01.maxnet.net.nz cannot access /plugins
err: Permission denied: Cannot access mount[plugins]
info: mount[plugins]: defaulting to no access for asterisk01.maxnet.net.nz
warning: mount[plugins]: asterisk01.maxnet.net.nz cannot access /plugins
err: Permission denied: Cannot access mount[plugins]

History

#1
Updated by Paul Lathrop over 2 years ago

  • Status changed from 1 to Closed
  • 7 set to invalid

Fujin,

Please take a look at the PluginsInModules page – it indicates that the old pluginsync method is deprecated, and describes the new model.

#2
Updated by AJ Christensen over 2 years ago

This appears to be a problem with the ‘allow’ wildcard globbing in the fileserver directive, notably with

allow *

it does NOT work, but with

allow *.maxnet.net.nz

it DOES work.

#3
Updated by AJ Christensen over 2 years ago

my other mountpoints do not exhibit this behaviour, that is, [files] and [modules] have worked perfectly with allow *.

#4
Updated by AJ Christensen over 2 years ago

Updated summary to reflect actual issue.

Also available in: Atom PDF