Issue #3368 has been updated by James Turnbull.

Status changed from Unreviewed to Needs more information

So the you have a resource like:

<pre>
cron { "cronjob":
  blah => blah,
  user => 'puppet',
  ensure => present,
}
</pre>

and then change it to:

<pre>
cron { "cronjob":
  blah => blah,
  user => 'root',
  ensure => present,
}
</pre>

?

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
----------------------------------------
Bug #3368: Cron names/titles not unique between users
http://projects.puppetlabs.com/issues/3368

Author: Benjamin Kite
Status: Needs more information
Priority: Normal
Assigned to: 
Category: cron
Target version: 
Affected version: 0.25.4
Keywords: 
Branch: 


1. created a cronjob with puppet name "joe" belonging to user "puppet" 
2. 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



-- 
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.

Reply via email to