Bug #3368
Cron names/titles not unique between users
| Status: | Duplicate | Start date: | 03/15/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | cron | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
- created a cronjob with puppet name “joe” belonging to user “puppet”
- changed cronjob user to “root” in manifest
Result is that puppet “sees” the cronjob owned by “puppet” and creates the new one as “root” but does not delete the former crontab entry. The next pass, puppet does the same thing, now making a second entry in the root crontab. The result is that each pass creates a new cronjob and the cronjobs multiply until an aggressive (i.e. multiple runs) ensure => absent is applied.
This is under CentOS release 5.2
Related issues
History
Updated by James Turnbull almost 2 years ago
- Status changed from Unreviewed to Needs More Information
So the you have a resource like:
cron { "cronjob":
blah => blah,
user => 'puppet',
ensure => present,
}
and then change it to:
cron { "cronjob":
blah => blah,
user => 'root',
ensure => present,
}
?
So firstly, this won’t delete the old entry. Effectively this is a new entry – and this makes logical sense to me – you could be creating multiple cron jobs with different users – how would Puppet know they are the same?
The latter problem though of multiple entries being created seems like a bug though. Can you add some master and client logs (—verbose —debug —trace) and the contents of your crontab file?
Thanks
Updated by Nigel Kersten 10 months ago
- Status changed from Needs More Information to Duplicate
Multiple entries issue is duplicated in #3010