puppet not running regularly on quantum build slave
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Core Infrastructure |
Fix Released
|
Undecided
|
Joseph Heck |
Bug Description
I found that puppet wasn't running regularly on the quantum build slave (50.57.114.73).
* had updated a manifest for the slave to add a package, 3 days later package still wasn't there
* logged in to slave, verified package wasn't here
* last entry in /tmp/manifest.log was 6 days prior
* reviewed Cron job - think I spotted an error in the flock command there
Cron job looks to be created by Puppet, but couldn't find the relevant manifest to make a patch to it. I foudn I could invoke Puppet remotely, did so - that replaced the existing crontab with the following:
# HEADER: This file was autogenerated at Tue Aug 30 17:14:30 +0000 2011 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: updatepuppet
*/15 * * * * sleep $((RANDOM\%600)) && cd /root/openstack
Since then, has been running every 15 min.
This bug is simply to track/ask the question: Any other hosts still out there with a broken (i.e. using Flock incorrectly) puppet crontab?
Chatted with James Blair on IRC today - Quantum appears to have just been a missed build slave, all the others have already had this issue resolved.