Jacob
Thanks for confirming that.
There might be another related bug: when I changed the ensure =>
mtime, it still failed:
/usr/bin/puppet:19:in `load'
/usr/bin/puppet:19
err:
/Stage[main]/Emb/File[/opt/jetty-distribution-7.4.2.v20110526.tar.gz]/ensure:
change from absent to file failed: Could
Well, it turns out that it's definitely a puppet bug.
The streaming checksumming that's used doesn't actually only look at the
first 512 characters like the static checksumming that's used for
verifying the file on disk does.
http://projects.puppetlabs.com/issues/8385
--
Jacob Helwig
On Tue, 1
Jacob
Thanks. I did that, the checksum is a3f7372d40abae273d2680b650ca4715.
This is the second checksum in the error, what did 1st checksum came
from? The file itself never changed during my tests.
What is the next step?
Thanks
Haitao
On Tue, Jul 12, 2011 at 9:53 AM, Jacob Helwig wrote:
> On
On Tue, 12 Jul 2011 08:41:24 -0700, Haitao Jiang wrote:
>
> This happens to Puppet 2.7.1 (both master and client). I have a file
> resource that I set to ensure => absent, Puppet removed it correctly
> with info line that it has a duplicate entry in the filebucket. I then
> changed the ensure => p
This happens to Puppet 2.7.1 (both master and client). I have a file
resource that I set to ensure => absent, Puppet removed it correctly
with info line that it has a duplicate entry in the filebucket. I then
changed the ensure => present, the agent run gave me following error:
/usr/bin/puppet:19
