Hi,

fwiw, I still use quite a lot of 2.7, when there was a standalone
filebucket (not puppet filebucket). This defaulted to clientbucket just
fine.

I suspect you can solve this by adding a [filebucket] section to
puppet.conf. Although I'm not sure whether this should be considered a
workaround rather than a solution.

Have you taken a look at jira to see if there is a ticket for this?
Otherwise, you may want to open one, see if the maintainers recognize
this as a problem or if there is a larger idea behind the design.

Regards,
Felix

On 01/14/2014 10:06 PM, Martin Langhoff wrote:
> Background I am using puppet via direct invokation of puppet apply
> path/to/manifest.pp -- no puppet server involved. Puppet is 3.1.1 on
> RHEL6.x and CentOS6.x boxes.
> 
> I needed to study a file change, coming from a concat. Looking at the
> report, I had the hash. This did not work:
> 
> # puppet filebucket get --local d49537fd4cd4a5e588b2775f25f511e6
> Error: Could not run: File not found
> 
> instead, this does work (but how would one know the right bucket?):
> 
> # puppet filebucket  get -b /var/lib/puppet/clientbucket  --local
> d49537fd4cd4a5e588b2775f25f511e6
> 
> OTOH, this Just Works:
> 
> # puppet filebucket backup --local  /etc/motd
> /etc/motd: d41d8cd98f00b204e9800998ecf8427e
> 
> # puppet filebucket get --local d41d8cd98f00b204e9800998ecf8427e
> 
> However, looking into /var/lib/puppet is is clear that they use
> different buckets. Using puppet apply will use
> /var/lib/puppet/clientbucket , while using puppet filebucket --local
> will use /var/lib/puppet/bucket .
> 
> In my case I used strace and find to figure out where things were
> going, which is hardly recommendable.
> 
> cheers,

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52DD2DC6.3000108%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to