Issue #3112 has been reported by Mark Mealman.
----------------------------------------
Bug #3112: Problem with adding and removing crons
http://projects.reductivelabs.com/issues/3112
Author: Mark Mealman
Status: Unreviewed
Priority: Normal
Assigned to:
Category:
Target version:
Affected version: 0.25.3
Keywords:
Branch:
Here's the cron in question:
cron {
upgrade_puppet:
command => "/root/upgrade_puppet.sh",
user => root,
hour => 9,
minute => 10,
ensure => present
}
Here's the error produced by puppet:
debug: //base_ec2/Cron[upgrade_puppet]: Changing ensure
debug: //base_ec2/Cron[upgrade_puppet]: 1 change(s)
notice: //base_ec2/Cron[upgrade_puppet]/ensure: created
debug: Flushing cron provider target root
"-":5: bad hour
errors in crontab file, can't install.
I was using cron bash scripts to upgrade puppet across 70 servers from 0.25.1
to 0.25.3. 0.25.1 can install, modify and remove the cron fine, but 0.25.3
throws this error.
Here's the full crontab:
# HEADER: This file was autogenerated at Mon Jan 25 16:31:33 -0500 2010 by
puppet.
# HEADER: While it can still be managed manually, it is definitely not
recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: backup_app
45 3 * * * /usr/local/bin/backup_app.pl
I can manually edit the crontab fine via 'crontab -e'
--
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://reductivelabs.com/redmine/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.
