Bug #14738

reprepro-related cron mails shouldn't be sent to sysadmins

Added by groente 2017-09-29 11:58:04 . Updated 2017-11-28 11:44:35 .

Status:
Resolved
Priority:
Normal
Assignee:
groente
Category:
Infrastructure
Target version:
Start date:
2017-09-29
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

reprepro-time-based-snapshots cronjobs currently mail to tails-sysadmins, whereas tails-rm would be a more suitable destination. Same for the “Deleting vanished identifier” email from tails-update-reprepro-config.


Subtasks


Related issues

Blocks Tails - Feature #13242: Core work: Sysadmin (Maintain our already existing services) Confirmed 2017-06-29

History

#1 Updated by intrigeri 2017-09-29 13:17:34

  • Description updated
  • Target version set to Tails_3.3

I’ll try to take a look during this cycle as it should be trivial, but no big deal if that gets postponed a bit.

#2 Updated by intrigeri 2017-09-29 13:18:33

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

#3 Updated by intrigeri 2017-10-05 08:17:43

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • QA Check set to Ready for QA

Hopefully fixed. I’m not 100% sure this change will be sufficient; we’ll see.

#4 Updated by intrigeri 2017-10-06 06:23:09

  • QA Check changed from Ready for QA to Dev Needed

Oops, I forgot the “Deleting vanished identifier” email from tails-update-reprepro-config.

#5 Updated by intrigeri 2017-10-08 04:46:24

  • QA Check changed from Dev Needed to Ready for QA

intrigeri wrote:
> Oops, I forgot the “Deleting vanished identifier” email from tails-update-reprepro-config.

Implemented, let’s see how it goes next time a branch is deleted. I’ll push a branch, wait for its APT suite to be created, and then will delete it.

#6 Updated by intrigeri 2017-10-08 04:54:31

  • Assignee changed from intrigeri to groente
  • % Done changed from 10 to 80

Works!

groente, if you want to review this:

#7 Updated by anonym 2017-11-15 11:30:58

  • Target version changed from Tails_3.3 to Tails_3.5

#8 Updated by groente 2017-11-28 10:38:00

  • Assignee changed from groente to intrigeri
  • QA Check changed from Ready for QA to Info Needed

i like the consistent recipient parameter, but shouldn’t it be set to tails-rm@boum.org instead of root or am i missing something here?

#9 Updated by intrigeri 2017-11-28 11:03:44

  • Assignee changed from intrigeri to groente
  • QA Check changed from Info Needed to Ready for QA

groente wrote:
> i like the consistent recipient parameter, but shouldn’t it be set to tails-rm@boum.org instead of root or am i missing something here?

I disagree about setting the default value for this parameter to one of our mailing lists: I want new contributors who replicate our setup locally to receive the corresponding email, instead of sending it to us.

Keep in mind this is merely the default value. We override it in our production setup: as my merge request said, see “commit 6a891cac0981ad8ad9df3af25fa9a808bf6a636f in our manifests repo” (and perhaps learn a tiny bit about Hiera? it’s a cool tool and we’re using it a lot :)

#10 Updated by groente 2017-11-28 11:21:19

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100
  • QA Check changed from Ready for QA to Pass

well, that answers the question whether i missed something :) thanks!

#11 Updated by intrigeri 2017-11-28 11:44:35

> well, that answers the question whether i missed something :) thanks!

:)