Jira (PUP-2976) File { checksum => .. } doesn't work

Mark Schmick (JIRA) Mon, 27 Oct 2014 11:12:34 -0700

Title: Message Title

Mark Schmick commented on an issue

Ping … when will a Fix Version be assigned? This is egregious since "checksum" is now broken for anything but "md5". And since that's the default, you might as well say using checksum breaks file resources, since if you use it at all to override "md5", you always get a mis-match because the server only does md5. For example:

file { "chroot-20070718.tar":

  ensure   => present,

  path     => "${release_account::redhat::home}/chroot-20070718.tar",

  source   => "/root/puppet/modules/release_account/files/chroots/${::osfamily}/chroot-20070718.tar",

  checksum => sha256lite,

Results in:

Notice: /Stage[main]/Release_account::Redhat::Chroot/File[chroot-20070718.tar]/content: current_value

   {sha256lite}3b155333d1cb1ed4e96f791c16dda06d95c47ded1b206240ed61c2c09f1426ba, should be

   {md5}d41d8cd98f00b204e9800998ecf8427e (noop)

Note that client-side checksum is {sha256lite} while server-side persists in using {md5}. This happens with any non-"md5" value of checksum: mtime, md5lite, etc.

Add Comment

Puppet /

PUP-2976

site.pp:
{code:none}
file {
    "/tmp/ultravnc.msi":
        source => "puppet:///repos/MSIs/UltraVnc_10962_x64.msi",
        checksum => 'md5lite';
}
{code}

{code:none}
[[email protected] MSIs]# puppet agent --test --environment=dmitchell --server=releng-puppet1.srv.releng.scl3.mozilla.com
Info: Retrieving plugin...

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2976) File { checksum => .. } doesn't work

Reply via email to