Your message dated Sat, 16 Mar 2013 23:38:25 +0000
with message-id <[email protected]>
and subject line Bug#698294: fixed in puppet 2.7.18-4
has caused the Debian Bug report #698294,
regarding puppet: Checksum mismatch when copying followed symlinks (upstream 
#7680)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
698294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698294
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: puppet
Version: 2.7.18-2
Severity: important

Dear maintainers,

I am building a number of Wheezy-based servers for my organisation and
have run into what is for us a show-stopper Puppet bug. The bug does not
appear in Squeeze.

Consider the following 'file' resource:

file { "/tmp/example":
    source  => "puppet:///modules/example/example.$fqdn",
    links   => follow,
}

If, on the puppetmaster,
/etc/puppet/modules/example/files/example.<fqdn> were a symlink to
another file, the file may not be created on the puppet client with an
error indicating a mismatched checksum. The error might look like:

err: /Stage[pre]/Example/File[/tmp/example]/ensure: change from absent
to present failed: Could not rename temporary file
/tmp/example.puppettmp_4293 to /tmp/example:
File written to disk did not match checksum; discarding changes ( vs
{md5}d41d8cd98f00b204e9800998ecf8427e) at
/etc/puppet/modules/example/manifests/init.pp:12 at
/etc/puppet/modules/example/manifests/init.pp:12

If the file is created already, for example by using touch to create an
empty file, Puppet will not touch the file at all and will fail to
update its contents - silently. When using 'puppet agent --test
--verbose --debug' or 'puppetd -tvd', there is no mention of the file in
the output of the command, but the resource is present in reports on our
Puppet Dashboard and marked as unchanged.

Applying the patch [1] in the upstream bug [2] to the client resolves
the issue for us.

As the upstream bug appears to be being ignored completely by the
upstream maintainers, can you please carry the patch in the Debian package?

[1] - http://projects.puppetlabs.com/issues/7680#note-6
[2] - http://projects.puppetlabs.com/issues/7680

Best regards,
Chris

-- System Information:
Debian Release: 7.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages puppet depends on:
ii  dpkg           1.16.9
ii  puppet-common  2.7.18-2
ii  ruby1.8        1.8.7.358-6

Versions of packages puppet recommends:
ii  ruby [rdoc]  4.9

Versions of packages puppet suggests:
pn  etckeeper   <none>
pn  puppet-el   <none>
pn  vim-puppet  <none>

-- Configuration Files:
/etc/default/puppet changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: puppet
Source-Version: 2.7.18-4

We believe that the bug you reported is fixed in the latest version of
puppet, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stig Sandbeck Mathisen <[email protected]> (supplier of updated puppet package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 15 Mar 2013 20:32:40 +0100
Source: puppet
Binary: puppet-common puppet puppetmaster-common puppetmaster 
puppetmaster-passenger vim-puppet puppet-el puppet-testsuite
Architecture: source all
Version: 2.7.18-4
Distribution: unstable
Urgency: low
Maintainer: Puppet Package Maintainers 
<[email protected]>
Changed-By: Stig Sandbeck Mathisen <[email protected]>
Description: 
 puppet     - Centralized configuration management - agent startup and compatib
 puppet-common - Centralized configuration management
 puppet-el  - syntax highlighting for puppet manifests in emacs
 puppet-testsuite - Centralized configuration management - test suite
 puppetmaster - Centralized configuration management - master startup and 
compati
 puppetmaster-common - Puppet master common scripts
 puppetmaster-passenger - Centralised configuration management - master setup 
to run under
 vim-puppet - syntax highlighting for puppet manifests in vim
Closes: 698294
Changes: 
 puppet (2.7.18-4) unstable; urgency=low
 .
   * Import upstream patch to fix puppet's handling of symbolic links
     (Closes: #698294)
Checksums-Sha1: 
 4d958db9f8769774698545d19338df58c086254c 1817 puppet_2.7.18-4.dsc
 0d44392a1cb16f5f2c145bed5915e393f10de8b5 57657 puppet_2.7.18-4.debian.tar.gz
 5598f704e2135ff28efdf7346d0c6f05eaed2438 1017010 puppet-common_2.7.18-4_all.deb
 a17404f7abfaac14c762a688c1fda1f26fc47834 269444 puppet_2.7.18-4_all.deb
 62ad745394ddebfa059c1624ad2eed54c8e1a8a4 265990 
puppetmaster-common_2.7.18-4_all.deb
 a0da2878fe8152fa2ea7449a80918d7c86410c00 261962 puppetmaster_2.7.18-4_all.deb
 759f092dcfb7ef5ca69ce46c300da9956ba4e6ed 260474 
puppetmaster-passenger_2.7.18-4_all.deb
 8a242bdc6add33f64298b4520f29baf5652aae91 260640 vim-puppet_2.7.18-4_all.deb
 25feea67a30accd6ad362305d1142d0499a07d94 261488 puppet-el_2.7.18-4_all.deb
 443af84c7e774cbc95d570eb227387d6285907fc 1155776 
puppet-testsuite_2.7.18-4_all.deb
Checksums-Sha256: 
 aabc361b39b2fa38207e8c5857bfa50fae23ab2ad74d87b35fe8c9e43ebfb2ca 1817 
puppet_2.7.18-4.dsc
 427325aa5fe70851bcf1668ef17e9be76c4ed5843fa2fb9f5069436a38702602 57657 
puppet_2.7.18-4.debian.tar.gz
 e322e4ec3cf4166546087488b420be5285ffa464fd783bcf962e8014362aa8b0 1017010 
puppet-common_2.7.18-4_all.deb
 4926c0ce89c66bb8df8fad5cd17ea770c083e6449a1a96b73fb14c122a1bea5a 269444 
puppet_2.7.18-4_all.deb
 397d17c9e1878e0c6b6f2109c3a1852aa6a94bc8a8407a4b555b224916c65699 265990 
puppetmaster-common_2.7.18-4_all.deb
 57a7c2658a3fcce57c69c8da9f8037ec38bb1f7a030d6c2cebcfe06f798c08bc 261962 
puppetmaster_2.7.18-4_all.deb
 e09a9512e4f7096d67785cff649c18d0207a2cb2b0374f3c02cbe6f216f47bff 260474 
puppetmaster-passenger_2.7.18-4_all.deb
 63c7e467c40b6faaaeccb27b004e814a4ef0253b778a7e6c899a1cc88331b01a 260640 
vim-puppet_2.7.18-4_all.deb
 ce74616a420b27d5df85b57243429c6311250d9db6c3b18fdddb5eed1a0b001b 261488 
puppet-el_2.7.18-4_all.deb
 afcbb4589d05d0865a35856497f7fd3e1185752d5af535ac77a0b57668e1b82b 1155776 
puppet-testsuite_2.7.18-4_all.deb
Files: 
 0cdb65496f8130a1187b9c187d9b3ecc 1817 admin optional puppet_2.7.18-4.dsc
 0a77664adb484ba16f2f7cee9586d408 57657 admin optional 
puppet_2.7.18-4.debian.tar.gz
 fc617278da4dbedd6061ced728518b15 1017010 admin optional 
puppet-common_2.7.18-4_all.deb
 7ebc5113fb712fe9bc004c3865f8b9a5 269444 admin optional puppet_2.7.18-4_all.deb
 4f8aedf66d04dd1422f545e7faf62ac5 265990 admin optional 
puppetmaster-common_2.7.18-4_all.deb
 be2113641d2ab86d063ffbe04e0fe209 261962 admin optional 
puppetmaster_2.7.18-4_all.deb
 75113869557236e52e00c4c04e7c5b2d 260474 admin optional 
puppetmaster-passenger_2.7.18-4_all.deb
 fce2fd1744305d12c52f446bbbe3d59b 260640 admin optional 
vim-puppet_2.7.18-4_all.deb
 bbcde29ee7428c58c3669f6ffbc03d21 261488 admin optional 
puppet-el_2.7.18-4_all.deb
 a5696ce915a6cb5db945a3031d96c54b 1155776 admin optional 
puppet-testsuite_2.7.18-4_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlFDiP0ACgkQQONU2fom4u4DFACfaan0hbT4ZuJuBZJ0eMhbcN8p
45cAoKLuf0RIh49F+9Zk+k7wRrvdp/ul
=UPC0
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to