The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Bug #6001

0.24.8 client to 2.6.4 server has Fileset path error

Added by James Turnbull over 5 years ago. Updated about 3 years ago.

Status:DuplicateStart date:01/25/2011
Priority:UrgentDue date:
Assignee:Nigel Kersten% Done:


Target version:2.6.5
Affected Puppet version:0.24.8 Branch:
Keywords: customer

We've Moved!

Ticket tracking is now hosted in JIRA:


[0;37mdebug: Calling fileserver.list[0m
/usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/client.rb:115:in `execute'
/usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/client.rb:148:in `make_rpc_call'
/usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/client.rb:39:in `list'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/proxy.rb:15:in `send'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/proxy.rb:15:in `list'
/usr/lib/ruby/site_ruby/1.8/puppet/type/file.rb:864:in `sourcerecurse'
/usr/lib/ruby/site_ruby/1.8/puppet/type/file.rb:855:in `each'
/usr/lib/ruby/site_ruby/1.8/puppet/type/file.rb:855:in `sourcerecurse'
/usr/lib/ruby/site_ruby/1.8/puppet/type/file.rb:719:in `recurse'
/usr/lib/ruby/site_ruby/1.8/puppet/type/file.rb:340:in `eval_generate'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:193:in `eval_generate'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:228:in `eval_resource'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:310:in `evaluate'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:426:in `thinmark'
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:425:in `thinmark'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:309:in `evaluate'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:303:in `collect'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:303:in `evaluate'
/usr/lib/ruby/site_ruby/1.8/puppet/node/catalog.rb:124:in `apply'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:331:in `download'
/usr/lib/ruby/1.8/timeout.rb:67:in `timeout'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:330:in `download'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:369:in `getplugins'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:192:in `getplugins'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:133:in `getconfig'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:245:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:426:in `thinmark'
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:425:in `thinmark'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:244:in `run'
/usr/lib/ruby/1.8/sync.rb:230:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:237:in `run'
[1;35merr: /File[/var/lib/puppet/lib]: Failed to generate additional resources during transaction: Fileset paths must be fully qualified[0m

Related issues

Duplicates Puppet - Bug #5221: 0.24/2.6 pluginsync broken: "Fileset paths must be fully ... Closed 11/08/2010


#1 Updated by Nigel Kersten over 5 years ago

Where did this come from?

Did it used to work with earlier versions of 2.6.x ?

#2 Updated by James Turnbull over 5 years ago

I’m unsure. We didn’t do a lot of 0.24.8 with 2.6.x testing so I am concerned it was missed. Going to see if the patch for #5221 fixes the issue.

#3 Updated by James Turnbull over 5 years ago

  • Status changed from Accepted to Duplicate

Duplicate of #5221.

#4 Updated by Vincent Bernat about 5 years ago

  • Status changed from Duplicate to Re-opened

Patch in bug #5221 solves this issue.

However, the patch needs to be applied to all clients. I still have a lot of clients using 0.24.5 and I don’t want to update them all. I suppose there is a dependency that is generated with a “/” at the end on the server side (since everything was working fine with 0.24.5 puppetmaster). Maybe this bug could be fixed by correcting this dependency?

#5 Updated by R.I. Pienaar about 5 years ago

I can confirm this bug, 0.24.8 client to 2.6.4 master pluginsync fails.

#6 Updated by Nigel Kersten about 5 years ago

  • Status changed from Re-opened to Duplicate

Still a duplicate.

#7 Updated by Charlie Sharpsteen about 3 years ago

  • Keywords set to customer

Also available in: Atom PDF