Don't run Puppet via cron on isotesters
We keep rebooting them, so cron isn’t a suitable solution to ensure we run Puppet often enough. And these systems keep creating/deleting network interfaces, which confuses Puppet a bit and results in sysadmins receiving useless error email.
Blocks Tails -
#3 Updated by bertagaz 2017-02-27 13:26:24
- Status changed from In Progress to Resolved
- Assignee deleted (
- % Done changed from 50 to 100
- QA Check deleted (
Ready for QA)
> Done (differently though) MR submitted upstream. Feel free to review it yourself there :)
Puppet oneshot service runs seems consistent with isotesters uptime, so I guess that’s a sign that your code works. :)
Seems that your mr will be merged soon too, so let’s consider this ticket as done. Nice catch, congrats!
#4 Updated by intrigeri 2017-04-11 10:34:41
- Status changed from Resolved to In Progress
- Assignee set to intrigeri
- Target version changed from Tails_2.11 to Tails_2.12
- % Done changed from 100 to 80
Crap, this has been causing problems since I’ve applied this change: our isotesters don’t reboot often enough so
puppetlast complains (the warning threshold is 2 hours only). I’ve bumped that threshold to 12 hours, we’ll see if it’s enough.