Issue #10063 has been reported by Igor ..
----------------------------------------
Bug #10063: cron resource violates resource ordering
https://projects.puppetlabs.com/issues/10063
Author: Igor .
Status: Unreviewed
Priority: Normal
Assignee:
Category: cron
Target version:
Affected Puppet version: 2.7.3
Keywords: cron ordering
Branch:
Consider the following class
<pre>
class broken_cron {
cron { 'myjob':
command => "/usr/local/sbin/myjob",
user => root,
minute => "22"
hour => "5"
ensure => present
}
# Try and cleanup crontab -- this is broken in a rather surprising way!
exec { 'crontab -l|grep -v myjob|crontab -':
unless => "crontab -l|grep '^# Puppet Name: myjob'",
path => "/bin:/usr/bin",
before => Cron['myjob']
}
}
</pre>
if this applied when crontab already contains myjob but with different time
settings than specified in the cron resource, crontab will end up containing
the job twice. It seems cron type is prefetching the contents of crontab before
the exec runs despite the explicit ordering.
--
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.
