Issue #4337 has been reported by Alan Barrett.
----------------------------------------
Bug #4337: filebucket is confused about configuration
http://projects.puppetlabs.com/issues/4337
Author: Alan Barrett
Status: Unreviewed
Priority: Normal
Assigned to:
Category:
Target version:
Affected version: 0.25.5
Keywords:
Branch:
The filebucket program doesn't seem to know about the default location of the
clientbucket.
Log messages when a file is replaced by puppetd:
<pre>
notice: //File[/tmp/example]/checksum: checksum changed
'{md5}03b9e3de079048833a5464b926c52456' to
'{md5}06312662dbb9c9f84adea238caa7ba4b'
info: //File[/tmp/example]: Filebucketed /tmp/example to puppet with sum
06312662dbb9c9f84adea238caa7ba4b
notice: //File[/tmp/example]/content: content changed
'{md5}06312662dbb9c9f84adea238caa7ba4b' to
'{md5}03b9e3de079048833a5464b926c52456'
</pre>
It did actually work:
<pre>
# ls -l
/var/puppet/clientbucket/0/6/3/1/2/6/6/2/06312662dbb9c9f84adea238caa7ba4b
total 10
-r--r----- 1 root root 3111 Jul 22 19:14 contents
-rw-rw-r-- 1 root root 20 Jul 22 19:14 paths
</pre>
filebucket thinks that the file was not saved:
<pre>
# /usr/local/bin/filebucket --local restore /tmp/example
06312662dbb9c9f84adea238caa7ba4b
err: Could not find file with checksum 06312662dbb9c9f84adea238caa7ba4b
</pre>
Without the --local flag it tries to contact a server, but it is using the
built-in default server name "puppet" instead of the server defined in the
[puppetd] section of /etc/puppet.conf):
<pre>
# /usr/local/bin/filebucket restore /tmp/example
06312662dbb9c9f84adea238caa7ba4b
err: Could not find server : getaddrinfo: node name or service name not known
Could not run: Could not find server puppet
</pre>
Passing a "-b" option makes it work;
<pre>
# /usr/local/bin/filebucket -b /var/puppet/clientbucket restore /tmp/example
06312662dbb9c9f84adea238caa7ba4b && echo ok
ok
# md5 /tmp/example
MD5 (/tmp/example) = 06312662dbb9c9f84adea238caa7ba4b
</pre>
Please make the filebucket command's defaults match the defaults used by
puppetd, or make it query the puppet configuration, or look in the cached
catalog for information about filebucket locations; essentially, it would be
nidce if a simple invocation of "filebucket restore $filename $md5" worked
without the user having to add any options.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
