Bug #13134

The Debian mirror used as upstream for our time-based snapshots is buggy

Added by intrigeri 2017-06-24 17:52:32 . Updated 2017-06-30 06:20:53 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2017-06-24
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

This week we’ve seen this every day: aptmethod error receiving 'http://ftp-osl.osuosl.org/debian/dists/stretch/InRelease': '404 Not Found [IP: 140.211.166.134 80]'. Which incidentally allowed us to discover Bug #12829. I guess we need to switch to another mirror.


Subtasks


Related issues

Related to Tails - Bug #12829: FTBFS due to buggy APT sources set in Vagrant build box by the provision script Resolved 2017-06-21
Related to Tails - Bug #12454: Always use the same Debian mirror for time-based APT snapshots Resolved 2017-04-18
Blocks Tails - Feature #13232: Core work 2017Q2: Sysadmin (Maintain our already existing services) Resolved 2017-06-29

History

#1 Updated by intrigeri 2017-06-24 17:52:56

commit e237c1f57c0245cacf74dede19739a8add498d49 in puppet-tails.git will help you understand where this comes from.

#2 Updated by intrigeri 2017-06-25 10:10:11

  • related to Bug #12829: FTBFS due to buggy APT sources set in Vagrant build box by the provision script added

#3 Updated by intrigeri 2017-06-25 12:39:44

  • related to Bug #12454: Always use the same Debian mirror for time-based APT snapshots added

#4 Updated by intrigeri 2017-06-25 12:45:09

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

This is one of the two reasons why our APT snapshots for the debian archive stopped updating, so I want to fix it ASAP.

I don’t see any InRelease file on http://ftp-osl.osuosl.org/debian/dists/stretch/, indeed. But that mirror does seem up-to-date. Actually, it seems expected that Debian stable dists don’t have InRelease, and we had GetInRelease: no set for Jessie already. Will do the same for Stretch.

#5 Updated by intrigeri 2017-06-25 12:48:36

  • % Done changed from 10 to 20
  • QA Check set to Ready for QA

Done + deployed, let’s see how it goes.

#6 Updated by intrigeri 2017-06-25 14:42:36

  • Assignee changed from intrigeri to bertagaz
  • % Done changed from 20 to 50

Seems to be fixed, please review & check we don’t get such email from cron 4 times a day anymore.

#7 Updated by bertagaz 2017-06-25 16:10:37

  • Assignee changed from bertagaz to intrigeri
  • % Done changed from 50 to 20

intrigeri wrote:
> Seems to be fixed, please review & check we don’t get such email from cron 4 times a day anymore.

Thanks for the fix! I spent some time yesterday when I noticed this trying to get why there were no InRelease file in the Debian mirrors, but couldn’t find anything, nor how to avoid this 404. I had to run elsewhere then. I’ll look tomorrow if we had such emails again.

#8 Updated by intrigeri 2017-06-26 07:08:57

  • Assignee changed from intrigeri to bertagaz

(I guess you reassigned to me by mistake.)

#9 Updated by bertagaz 2017-06-26 07:48:57

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

intrigeri wrote:
> (I guess you reassigned to me by mistake.)

Yes sorry. No new emails since then, so let’s consider this as (partly) resolved. Next step is Feature #12002, on my plate.

#10 Updated by intrigeri 2017-06-29 09:53:39

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

#11 Updated by intrigeri 2017-06-30 06:20:53

  • Target version changed from Tails_3.1 to Tails_3.0.1