Project

General

Profile

Bug #15557

Document workaround for partially applied automatic upgrade

Added by intrigeri about 2 months ago. Updated about 19 hours ago.

Status:
Confirmed
Priority:
Elevated
Assignee:
Category:
-
Target version:
Start date:
04/30/2018
Due date:
% Done:

0%

QA Check:
Info Needed
Feature Branch:
Type of work:
End-user documentation
Blueprint:
Starter:
Affected tool:
Upgrader

Description

As we see on #14574 sometimes an automated upgrade is partially applied and as a result the upgraded system behaves weirdly. That is occuring a lot recently according to help desk, but I've found no way to fix it yet (there's a tentative fix ready in Git, that will be used first during the 3.9→3.10 upgrade but I'm not counting on it too much).

So IMO we should document a workaround: assuming I've upgraded to 3.6.2 and my Tails does not work anymore, I should add a line that contains "3.6.2.squashfs" (without the quotes) at the end of live/Tails.module (at the root of the Tails system partition). Adjust the version number depending on what version one is upgrading to, e.g. if users have the same problem after upgrading to 3.7, they should add a line that contains "3.7.squashfs" instead. Presumably this must be done from a non-Tails system (or from another, working Tails).


Related issues

Related to Tails - Bug #10347: Troubleshooting for automatic upgrades that fail to restart Confirmed 10/07/2015
Blocks Tails - Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing Confirmed 03/14/2018

History

#1 Updated by intrigeri about 2 months ago

  • Blocks Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing added

#2 Updated by intrigeri about 2 months ago

  • Priority changed from Normal to Elevated

(Help desk say lots of users are affected.)

#3 Updated by sajolida about 2 months ago

  • Description updated (diff)
  • Assignee changed from sajolida to cbrownstein

Cody: Do you think you can work on it this week?

I'll be super busy with the user testing of additional software :/

#4 Updated by sajolida about 1 month ago

Definitely related to #10347. So I'm assigning it to you as well.

This one might be tough, so tell me if you need help!

#5 Updated by sajolida about 1 month ago

  • Related to Bug #10347: Troubleshooting for automatic upgrades that fail to restart added

#6 Updated by bertagaz about 1 month ago

  • Target version changed from Tails_3.7 to Tails_3.8

#7 Updated by cbrownstein about 19 hours ago

  • Assignee changed from cbrownstein to intrigeri
  • QA Check set to Info Needed

intrigeri wrote:

As we see on #14574 sometimes an automated upgrade is partially applied and as a result the upgraded system behaves weirdly.

I'm trying to understand the symptoms of a partially-applied automatic upgrade. Can "behaves weirdly" be more definite? #14574 appears to be unrelated to this ticket. Is there a correct ticket I can reference?

So IMO we should document a workaround: assuming I've upgraded to 3.6.2 and my Tails does not work anymore, I should add a line that contains "3.6.2.squashfs" (without the quotes) at the end of live/Tails.module (at the root of the Tails system partition). Adjust the version number depending on what version one is upgrading to, e.g. if users have the same problem after upgrading to 3.7, they should add a line that contains "3.7.squashfs" instead. Presumably this must be done from a non-Tails system (or from another, working Tails).

What can the user expect after this is done?

Also available in: Atom PDF