Feature #17412

Drop the need for dedicated temporary storage space for IUKs on rsync.lizard

Added by intrigeri 2020-01-09 09:39:16 . Updated 2020-03-28 14:17:21 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:


That’s the second step of Feature #17385#note-2, i.e. make it so temporary data is stored directly in /srv during the release process.

One idea could be to:

  1. give every RM permission to SSH into rsync.lizard as the rsync_tails user, and point $HOME for this user somewhere under /srv
  2. adjust the release process so that all SSH operations done on rsync.lizard are done as the rsync_tails user
  3. drop the /home LV and migrate the corresponding data back to /


Related issues

Related to Tails - Feature #17385: Grow /home on rsync.lizard Resolved
Related to Tails - Feature #15287: Make it possible to reproducibly generate IUKs in CI Resolved 2018-02-05
Blocks Tails - Feature #13242: Core work: Sysadmin (Maintain our already existing services) Confirmed 2017-06-29


#1 Updated by intrigeri 2020-01-09 09:39:29

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

#2 Updated by intrigeri 2020-01-09 09:39:40

#3 Updated by intrigeri 2020-01-09 09:39:48

  • related to Feature #15287: Make it possible to reproducibly generate IUKs in CI added

#4 Updated by intrigeri 2020-01-09 09:39:55

  • Priority changed from Normal to Elevated

#5 Updated by intrigeri 2020-01-27 08:16:55

  • Status changed from Confirmed to In Progress
  • Feature Branch set to doc/17415-fix-IUK-generation-in-release-process

#6 Updated by intrigeri 2020-01-27 08:34:08

  • Status changed from In Progress to Needs Validation
  • Assignee changed from intrigeri to anonym
  • Type of work changed from Sysadmin to Code

In the end I did it differently: instead of a new, dedicated user, I’ve adjusted our code & release process to use a work directory under /srv.

#7 Updated by anonym 2020-02-11 15:26:51

  • Target version changed from Tails_4.3 to Tails_4.4

#8 Updated by CyrilBrulebois 2020-03-12 09:56:03

  • Target version changed from Tails_4.4 to Tails_4.5

#9 Updated by intrigeri 2020-03-28 08:03:22

  • Assignee changed from anonym to CyrilBrulebois

Reassigning to @CyrilBrulebois, who will exercise this code path during the 4.5 release process.

#10 Updated by CyrilBrulebois 2020-03-28 12:49:20

  • Assignee changed from CyrilBrulebois to intrigeri
  • Feature Branch deleted (doc/17415-fix-IUK-generation-in-release-process)

Well, I’m not sure I understand. The branch is gone, it’s been merged a while ago, and the relevant commit is available in:

# TIL git branch --contains
kibi@armor:~/work/clients/tails/release/release-checkout$ git branch --contains 4eb681c4
* testing

and even:

kibi@armor:~/work/clients/tails/release/release-checkout$ git describe --contains 4eb681c4

#11 Updated by intrigeri 2020-03-28 14:10:48

  • Assignee changed from intrigeri to CyrilBrulebois

> Well, I’m not sure I understand. The branch is gone, it’s been merged a while ago […]

Yep, I should have made my request clearer.

So, I have two questions:

  • Does commit:4eb681c4278f38a1727ad15346626d10bdfffb06 look sane to you?
  • Did you encounter any trouble recently (possibly caused by that commit) at the step of the release process that uses the copy-iuks-to-rsync-server-and-verify script?

#12 Updated by CyrilBrulebois 2020-03-28 14:17:21

  • Status changed from Needs Validation to Resolved

Oh, OK.

Yes, the commit looks sane to me, and I’m happy not to have that kind of extra dance anymore.

TBH this was rather well hidden behind the new IUK handling (copied from Jenkins because successfully reproduced there), and while I haven’t had to exercise the “manual upload” code path (fingers crossed), the overall change seems very fine.