Bug #12097

Don't run Puppet via cron on isotesters

Added by intrigeri 2016-12-29 10:23:53 . Updated 2017-04-15 17:00:47 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.12
Start date:
2016-12-29
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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.

Subtasks

Related issues

Blocks Tails - Feature #13232: Core work 2017Q2: Sysadmin (Maintain our already existing services) Resolved 2017-06-29

History

#1 Updated by intrigeri 2016-12-29 10:52:44

Implementation plan:

  • give tails::base a puppet_agent_run parameter, whose value can be cron or boot
  • create a puppet::run_agent_at_boot class, that manages a one-shot unit file that runs the Puppet agent at boot time

#2 Updated by intrigeri 2017-02-12 15:40:06

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to bertagaz
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

Done (differently though) MR submitted upstream. Feel free to review it yourself there :)

#3 Updated by bertagaz 2017-02-27 13:26:24

  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • % Done changed from 50 to 100
  • QA Check deleted (Ready for QA)

intrigeri wrote:
> 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.

#5 Updated by intrigeri 2017-04-12 11:09:34

12h wasn’t enough, let’s try 16 hours.

#6 Updated by intrigeri 2017-04-15 17:00:47

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 80 to 100

16h seems to be enough to avoid noisy cron email, even during pretty quiet times such as a freeze.

#7 Updated by intrigeri 2017-06-29 10:02:23

  • blocks Feature #13232: Core work 2017Q2: Sysadmin (Maintain our already existing services) added