Your message dated Mon, 16 Aug 2010 14:40:49 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-puppet-devel] Bug#593125: puppet: 2.6.0 produces
empty files on client with 2.5.x puppetmaster
has caused the Debian Bug report #593125,
regarding puppet: 2.6.0 produces empty files on client with 2.5.x puppetmaster
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.)
--
593125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593125
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: puppet
Version: 2.6.0-2
Severity: normal
Hello,
We run 4 squeeze freebsd servers, and the puppet clients talk to a lenny
+ bpo puppetmaster. When 2.6.0 migrated to squeeze, we started to get
empty files on the clients. The clients knew that the checksum was
non-empty, but never pulled the data down, eg:
notice: //Nagios::Client/File[/etc/nagios/nrpe.d/nrpe_dsa.cfg]/content: content
changed '{md5}d41d8cd98f00b204e9800998ecf8427e' to
'{md5}a5043ad9ae1e3173348704fffb001613'
(d41d8cd98f00b204e9800998ecf8427e is the md5sum of the empty string, and
a5043ad9ae1e3173348704fffb001613 is the correct md5sum of the file.
However, the file would still be 0 byte at the end of the puppet run.
Downgrading to the version below produces correct behavior.
Cheers,
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: kfreebsd-i386 (i686)
Kernel: kFreeBSD 8.1-1-686
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii adduser 3.112 add and remove users and groups
ii facter 1.5.7-1 a library for retrieving facts fro
pn libopenssl-ruby <none> (no description available)
ii libruby [libxmlrpc-ruby 4.5 Libraries necessary to run Ruby 1.
ii libshadow-ruby1.8 1.4.1-8 Interface of shadow password for R
ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip
ii puppet-common 0.25.4-2~bpo50+1 common files for puppet and puppet
ii ruby1.8 1.8.7.299-2 Interpreter of object-oriented scr
Versions of packages puppet recommends:
ii libaugeas-ruby1.8 0.3.0-1.1 Augeas bindings for the Ruby langu
ii ruby [rdoc] 4.5 An interpreter of object-oriented
Versions of packages puppet suggests:
pn puppet-el <none> (no description available)
pn vim-puppet <none> (no description available)
-- Configuration Files:
/etc/default/puppet changed:
START=no
exit 0
DAEMON_OPTS="-w 5 --factsync"
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello, and thanks for reporting an issue with the puppet package.
The problem you have encountered is known, and documented in the
upstream release notes:
,----[ http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes ]
| It is also important to note when upgrading that not all versions are
| backwards compatible. Newer clients may not work with older servers
| and vice-versa. Where possible backwards-compatibility is maintained
| but it’s not always totally successful. The best approach is to
| ensure your master and clients are the same version. When upgrading
| it is also recommended that you upgrade your master first.
`----
The situation is not ideal, but I'm going to close this bug in the
Debian Bug Tracker.
If you have any ideas about how the situation could be improved, please
open a bug, preferrably in the upstream bug tracker at
<http://projects.puppetlabs.com/projects/puppet/issues>
--
Stig Sandbeck Mathisen
pgpM6hlyNV1Qf.pgp
Description: PGP signature
--- End Message ---
