Bug #12010

puppetlast cronjob is too noisy, by assuming that all our systems are online 24/7

Added by intrigeri 2016-12-01 12:44:11 . Updated 2017-01-07 18:57:58 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails 2.10
Start date:
2016-12-01
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Recently we added a mobile, not-always-on system that’s managed by our Puppet master. This triggers one email from puppetlast everyday. We should fix this somehow, e.g. by giving puppetlast a list of managed systems that it should ignore.

Subtasks

History

#1 Updated by intrigeri 2016-12-01 12:44:53

  • Target version set to Tails 2.10

#2 Updated by intrigeri 2017-01-07 18:22:19

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

Got a plan: https://gitlab.com/shared-puppet-modules-group/puppet/issues/10

#3 Updated by intrigeri 2017-01-07 18:57:58

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

My plan was wrong, but there was a simpler solution. Done.