Cucumber Reports (no 2) - Feature: Upgrading an old Tails USB installation

Project	Number	Date
test_Tails_ISO_ignore-private-backports	2	08 Jul 2025, 06:19

	Steps	Scenarios	Features
Upgrading an old Tails USB installation	51	2	34	0	0	87	5	2	7	54:23.169	Failed

Tags: @product

Feature Upgrading an old Tails USB installation

As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process

Tags: @product

4:58.245

Scenario Installing an old version of Tails to a pristine USB drive

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.002

Steps

Given a computer 0.179

And I create a 7200 MiB disk named "old" 0.065

And I plug USB drive "old" 1.189

And I write an old version of the Tails USB image to disk "old" 1:10.792

When I start Tails from USB drive "old" with network unplugged 3:40.173

Then the boot device has safe access rights 3.959

And Tails is running from USB drive "old" 0.864

And there is no persistence partition on USB drive "old" 0.148

And process "udev-watchdog" is running 0.236

And udev-watchdog is monitoring the correct device 0.415

And I unplug USB drive "old" 0.221

Hooks

After features/support/hooks.rb:330 5.777

After features/support/hooks.rb:100 0.024

Tags: @product

5:49.616

Scenario Creating a persistent partition with the old Tails USB installation

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.016

Steps

Given a computer 0.341

And I start Tails from USB drive "old" with network unplugged and I login 4:20.006

Then Tails is running from USB drive "old" 2.070

And I create a persistent partition 1:5.728

And I take note of which tps features are available 3.821

Then a Tails persistence partition exists on USB drive "old" 1.176

And I shutdown Tails and wait for the computer to power off 16.471

Hooks

After features/support/hooks.rb:330 0.157

After features/support/hooks.rb:100 0.008

Tags: @product

7:39.446

Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.004

Steps

Given a computer 0.201

And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 5:46.903

Then Tails is running from USB drive "old" 9.178

And all tps features are active 4.131

When I write some files expected to persist 2.772

# Verify that our baseline for the next scenarios is sane

And all persistent filesystems have safe access rights 0.639

And all persistence configuration files have safe access rights 0.733

And all persistent directories from the old Tails version have safe access rights 9.332

And I take note of which tps features are available 1.798

And I shutdown Tails and wait for the computer to power off 10.698

# XXX: how does guestfs work vs snapshots?

Then only the expected files are present on the persistence partition on USB drive "old" 1:13.056

Hooks

After features/support/hooks.rb:330 0.145

After features/support/hooks.rb:100 0.007

Tags: @product

5:20.532

Scenario Upgrading an old Tails USB installation from another Tails USB drive

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.003

Steps

Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 49.885

And I log in to a new session 1:9.312

And I clone USB drive "old" to a new USB drive "to_upgrade" 2.255

And I plug USB drive "to_upgrade" 4.176

When I upgrade Tails to USB drive "to_upgrade" by cloning 2:19.221

Then the running Tails is installed on USB drive "to_upgrade" 55.167

And I unplug USB drive "to_upgrade" 0.249

And I unplug USB drive "__internal" 0.264

Hooks

After features/support/hooks.rb:330 12.951

After features/support/hooks.rb:100 0.000

Tags: @product

5:30.692

Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.013

Steps

Given a computer 0.681

And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 5:6.186

Then all tps features from the old Tails version are active 2.399

And Tails is running from USB drive "to_upgrade" 0.369

And the boot device has safe access rights 12.009

And the expected persistent files created with the old Tails version are present in the filesystem 5.005

And all persistent directories from the old Tails version have safe access rights 4.042

Hooks

After features/support/hooks.rb:330 1.494

After features/support/hooks.rb:100 0.010

Tags: @product @automatic_upgrade

1:29.546

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.004

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:29.546

Failed

Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And no SquashFS delta is installed 0.000

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000

And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000

And the file system changes introduced in version 6.3~testoverlayfs are not present 0.000

When the network is plugged 0.000

And Tor is ready 0.000

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000

And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000

Given I shutdown Tails and wait for the computer to power off 0.000

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000

Then Tails is running version 6.2~testoverlayfs 0.000

And all tps features are active 0.000

And the file system changes introduced in version 6.2~testoverlayfs are present 0.000

And only the 6.2~testoverlayfs SquashFS delta is installed 0.000

# Our IUK sets a release date that can make Tor bootstrapping impossible

Given Tails system time is magically synchronized 0.000

# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk

# but we need some way to force upgrading a second time in a row

# even if only the initially installed version is considered

And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000

When the network is plugged 0.000

And Tor is ready 0.000

Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000

And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000

Given I shutdown Tails and wait for the computer to power off 0.000

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000

Then Tails is running version 6.3~testoverlayfs 0.000

And all tps features are active 0.000

And the file system changes introduced in version 6.3~testoverlayfs are present 0.000

And only the 6.3~testoverlayfs SquashFS delta is installed 0.000

# Regression test for #17425 (i.e. the Upgrader would propose

# upgrading to the version that's already running)

Given Tails system time is magically synchronized 0.000

And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000

When the network is plugged 0.000

And Tor is ready 0.000

Then the Upgrader considers the system as up-to-date 0.000

# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)

And I successfully start the Unsafe Browser 0.000

And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000

Hooks

After features/support/hooks.rb:330 7.578

Output 1

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 04:13:59)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/2/artifact/build-artifacts/04:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/2/artifact/build-artifacts/04:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/2/artifact/build-artifacts/04:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/2/artifact/build-artifacts/04:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.000

Tags: @product @automatic_upgrade

23:35.088

Scenario Upgrading a Tails whose signing key is outdated

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.017

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.306

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.045

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.180

And the signing key used by the Upgrader is outdated 0.075

But a current signing key is available on our website 0.000

When the network is plugged 0.086

And Tor is ready 38.339

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:34.055

Tor

Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'

Hooks

After features/support/hooks.rb:330 5.722

Output 1

SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 04:37:42)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/2/artifact/build-artifacts/04:37:42_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/2/artifact/build-artifacts/04:37:42_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/2/artifact/build-artifacts/04:37:42_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/2/artifact/build-artifacts/04:37:42_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

After features/support/hooks.rb:100 0.000

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Upgrading an old Tails USB installation	51	2	34	0	0	87	5	2	7	54:23.169	Failed

Feature Report