Bug #15456

Upgrade Linux to 4.15.0-2

Added by intrigeri 2018-03-27 09:12:47 . Updated 2018-04-08 13:58:39 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Target version:
Tails_3.7
Start date:
2018-03-27
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Our devel branch FTBFS since Linux 4.15.0-1 was removed from sid. Let’s fix this on devel first and this will give us data points wrt. Bug #15435.

Subtasks

Related issues

Blocks Tails - Feature #13245: Core work 2018Q1: Foundations Team Resolved 2017-06-29
Blocked by Tails - Bug #15457: Upgrade Linux in Tails 3.6.2 Resolved 2018-03-22

History

#1 Updated by intrigeri 2018-03-27 09:14:30

  • Subject changed from Upgrade to Linux 4.15.0-2 to Upgrade Linux to 4.15.0-2
  • % Done changed from 0 to 10
  • Feature Branch set to bugfix/15456-Linux-4.15.0-2

#2 Updated by intrigeri 2018-03-27 09:14:41

  • blocks Bug #15435: Consider upgrading Linux in Tails 3.7 added

#3 Updated by intrigeri 2018-03-27 09:15:02

#4 Updated by intrigeri 2018-03-27 10:17:19

  • blocks Bug #15457: Upgrade Linux in Tails 3.6.2 added

#5 Updated by intrigeri 2018-03-27 14:36:09

  • % Done changed from 10 to 50

Full test suite locally passes except:

  • “Scenario: Upgrading Tails with Tails Upgrader through an incremental upgrade”: passed on Jenkins
  • “Scenario: Additional software packages are installed even without network”: never seen it pass locally, passed on Jenkins

#6 Updated by intrigeri 2018-03-27 17:50:53

  • blocked by deleted (Bug #15457: Upgrade Linux in Tails 3.6.2)

#7 Updated by intrigeri 2018-03-27 17:51:02

  • blocked by Bug #15457: Upgrade Linux in Tails 3.6.2 added

#8 Updated by intrigeri 2018-03-27 17:51:37

  • Assignee changed from intrigeri to anonym
  • QA Check set to Ready for QA
  • Feature Branch deleted (bugfix/15456-Linux-4.15.0-2)

See Bug #15457#note-6.

#9 Updated by bertagaz 2018-03-28 10:04:52

intrigeri wrote:
> * “Scenario: Additional software packages are installed even without network”: never seen it pass locally, passed on Jenkins

Never seen a bug report either. It works locally here and in Jenkins, and the only failures I’ve seen were Tor bootstrap problems. If there’s somethin’ else, I’d have been curious, but Feature #14596 rewrites this scenario anyway.

#10 Updated by intrigeri 2018-03-28 10:22:46

> Never seen a bug report either.

Yeah, sorry about this, I can only blame myself: I want to first investigate it a bit on my side because it seems I am the only one experiencing this problem, and reporting a bug you cannot reproduce would not be terribly useful (it would land back on my plate as “Info Needed” anyway :)

> It works locally here and in Jenkins, and the only failures I’ve seen were Tor bootstrap problems.
> If there’s somethin’ else, I’d have been curious, but Feature #14596 rewrites this scenario anyway.

IIRC it’s not anything else, it’s Tor bootstrapping problems. So I’ll wait for Feature #14596.

#11 Updated by bertagaz 2018-03-28 11:00:52

intrigeri wrote:
> > Never seen a bug report either.
>
> Yeah, sorry about this, I can only blame myself: I want to first investigate it a bit on my side because it seems I am the only one experiencing this problem, and reporting a bug you cannot reproduce would not be terribly useful (it would land back on my plate as “Info Needed” anyway :)

Hint: I see more of this kind of failure with the usual Chutney network used in the test suite. Lately, when setting V3AuthVotingInterval to something like 14400 in submodules/chutney/torrc_templates/authority.i I get close to none of this bootstrap errors. That makes sense: the consensus is not renewed very 10 seconds anymore which gives a much more stable tor network. The Tails VM Tor process gets a valid consensus at the first download attempt and bootstrap very much faster. I wanted to add a note on that on Bug #13541 and/or Bug #15160. It could even help for Feature #15211 a bit (reduce crypto operations).

#12 Updated by anonym 2018-03-29 10:05:15

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

#13 Updated by intrigeri 2018-03-29 16:37:55

> Hint: I see more of this kind of failure with the usual Chutney network used in the test suite. Lately, when setting V3AuthVotingInterval to something like 14400 in submodules/chutney/torrc_templates/authority.i I get close to none of this bootstrap errors.

Thanks, I’ve reported this on Bug #13541.

#14 Updated by intrigeri 2018-04-08 13:58:04

  • blocked by deleted (Bug #15435: Consider upgrading Linux in Tails 3.7)

#15 Updated by intrigeri 2018-04-08 13:58:39

  • Status changed from Fix committed to Resolved
  • Target version changed from Tails_3.9 to Tails_3.7

Done in 3.6.2.