Bug #17442

tails-bugs@ needs to get its expiry date pushed back

Added by CyrilBrulebois 2020-01-16 10:51:36 . Updated 2020-02-04 08:24:19 .

Status:
Resolved
Priority:
Elevated
Assignee:
intrigeri
Category:
Infrastructure
Target version:
Tails_4.3
Start date:
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Since yesterday, the stable branch exhibits a new failure in its test suite:

cucumber features/keys.feature:4 # Scenario: The shipped Tails OpenPGP keys are up-to-date

Looking at the shipped keys, one can see those set to expire in 2020:

  • tails-bugs: 2020-04-14 → this is the one that triggers the error * tails: 2020-10-07 → this could become a similar issue in 6 months

(Others don’t expire or expire in 2021, so are not an immediate issue.)

Not entirely sure who to assign this to. Tentatively picking the help desk, who should know?

Subtasks

Related issues

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

History

#1 Updated by emmapeel 2020-01-16 11:00:42

we never updated it yet, in frontdesk. not sure how to go about that… maybe there is a set of rules for updating expiration dates?

#2 Updated by intrigeri 2020-01-25 10:48:30

  • Assignee changed from Help Desk to zen
  • Target version set to Tails_4.3

> we never updated it yet, in frontdesk.

This is usually handled by our sysadmins, who host the last and maintain its private key (the fact list subscribers also have that private key is a side-effect of Schleuder bugs rather than an expression of a maintenance role) ⇒ assigning to the sysadmin who was on duty on Jan 16, and still is :)

#3 Updated by intrigeri 2020-01-25 10:52:59

(Just a poke to ensure zen gets a notification email about this :)

#4 Updated by intrigeri 2020-02-04 08:14:43

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

#5 Updated by intrigeri 2020-02-04 08:17:38

  • Assignee changed from zen to intrigeri
  • Priority changed from Normal to Elevated

This problem has forced developers to filter out the corresponding test suite failure every time they analyze Jenkins results since almost 3 weeks, so I’d like this to be resolved soon ⇒ will give it a try :)

#6 Updated by intrigeri 2020-02-04 08:24:19

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|69a48c8f05c77a146342c367de529abfbffe2aa0.