Issue #775 has been updated by Dan Carley.
Likewise, I've hit this.
Seemed to run fine for a while with the following:
<pre>
class someclass {
# TODO: Delete this later.
crontab { "something":
ensure => absent,
}
}
</pre>
Only upon changing `environment` did it start throwing the error:
<pre>
err: Could not prefetch cron provider 'crontab': No command, somehow at [..]
</pre>
As reported by two of the other commentators, a side effect was that crontab
resources from outside of `someclass` were incorrectly identified as being
`absent` and thus created duplicates.
----------------------------------------
Bug #775: Cron resources being deleted still require a command.
http://projects.puppetlabs.com/issues/775
Author: Matt Palmer
Status: Accepted
Priority: Low
Assigned to:
Category: cron
Target version: unplanned
Patch: None
Affected version: 0.25.1
Keywords:
Branch:
A resource spec like this:
<pre>
cron { run_update_etc_puppet:
ensure => absent,
user => root
}
</pre>
Results in an error like this on every Puppet run under 0.23.2:
<pre>
err: //hostname/class/Cron[run_update_etc_puppet]: Failed to retrieve current
state of resource: No command, somehow at
/etc/puppet/manifests/classes/class.pp:20
</pre>
I'm fairly certain that error didn't appear in 0.22.4, otherwise I would have
reported it then, too.
--
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.
