Bug #593

Puppet's cron type struggles with vixie-cron

Added by Peter Abrahamsen over 3 years ago. Updated 3 months ago.

Status:Accepted Start:
Priority:Normal Due date:
Assigned to:- % Done:

0%
Category:cron
Target version:Statler
Affected version:0.25.1 Branch:
Keywords:
Votes: 3

Description

After making a few changes to my cron job in my manifest, my crontab begins to look like:

# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Thu Apr 12 12:16:01 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $)
# HEADER This file was autogenerated at Thu Apr 12 12:16:01 -0700 2007 by puppet.
# HEADER While it can still be managed manually, it is definitely notrecommended.
# HEADER Note particularly that the comments starting with 'Puppet Name' should
# HEADER not be deleted, as doing so could cause duplicate cron jobs.
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Wed Apr 11 16:42:40 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $)
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Tue Apr 10 13:49:45 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $)
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Thu Apr  5 17:36:42 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $)
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.XXXXWxMPKB installed on Thu Apr  5 17:08:07 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $)
# Puppet Name: websync
*/10 * * * *

If puppet would put its notice just before the first job it manages, I think it would avoid this problem.

History

Updated by Luke Kanies about 3 years ago

  • Status changed from 1 to 2

Updated by Redmine Admin about 2 years ago

  • Status changed from 2 to Accepted

Updated by Luke Kanies over 1 year ago

  • Affected version set to 0.24.7

I swear we fixed this problem a long time ago (which is appropriate, given how old the ticket is), but this will have to wait until a later release, when we can assess all of the cron tickets at once.

Updated by Luke Kanies over 1 year ago

  • Target version changed from 0.25.0 to 2.6.0

Yes, I’m bumping again.

Can anyone by chance test this, to make sure it’s still broken? I’m so convinced I fixed it already.

Updated by Alexey Lapitsky over 1 year ago

0.24.7 is affected

Updated by Dan Carley 8 months ago

0.25.0 also affected.

Updated by James Turnbull 8 months ago

  • Affected version changed from 0.24.7 to 0.25.1

Updated by James Turnbull 6 months ago

  • Target version changed from 2.6.0 to Statler

Updated by Luke Kanies 3 months ago

  • Assigned to deleted (Luke Kanies)

Also available in: Atom PDF