Project Number Date
test_Tails_ISO_devel 3870 16 Jun 2025, 16:03

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 52 1 34 0 0 87 6 1 7 25:49.478 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
3:39.084
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 0.352
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 1:5.028
When I start Tails from USB drive "old" with network unplugged 2:27.652
Then the boot device has safe access rights 3.479
And Tails is running from USB drive "old" 0.580
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.453
And I unplug USB drive "old" 0.239
After features/support/hooks.rb:330 7.163
After features/support/hooks.rb:100 0.285
Tags: @product
3:57.366
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.212
Given a computer 0.966
And I start Tails from USB drive "old" with network unplugged and I login 2:27.969
Then Tails is running from USB drive "old" 0.569
And I create a persistent partition 1:6.588
And I take note of which tps features are available 4.934
Then a Tails persistence partition exists on USB drive "old" 3.645
And I shutdown Tails and wait for the computer to power off 12.690
After features/support/hooks.rb:330 0.837
After features/support/hooks.rb:100 0.100
Tags: @product
5:53.453
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.080
Given a computer 2.385
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:12.532
Then Tails is running from USB drive "old" 0.693
And all tps features are active 7.599
When I write some files expected to persist 6.726
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.348
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 3.868
And I take note of which tps features are available 0.645
And I shutdown Tails and wait for the computer to power off 13.858
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 1:4.340
After features/support/hooks.rb:330 0.335
After features/support/hooks.rb:100 0.033
Tags: @product
4:57.582
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.345
And I log in to a new session 43.953
And I clone USB drive "old" to a new USB drive "to_upgrade" 12.437
And I plug USB drive "to_upgrade" 4.528
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:42.564
Then the running Tails is installed on USB drive "to_upgrade" 51.196
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.318
After features/support/hooks.rb:330 3.853
After features/support/hooks.rb:100 0.000
Tags: @product
4:16.548
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:53.376
Then all tps features from the old Tails version are active 2.206
And Tails is running from USB drive "to_upgrade" 0.514
And the boot device has safe access rights 6.887
And the expected persistent files created with the old Tails version are present in the filesystem 10.288
And all persistent directories from the old Tails version have safe access rights 3.026
After features/support/hooks.rb:330 0.932
After features/support/hooks.rb:100 0.011
1:29.212
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:29.212
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72: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
After features/support/hooks.rb:330 8.838

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:22:23)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3870/artifact/build-artifacts/02:22:23_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_devel/3870/artifact/build-artifacts/02:22:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3870/artifact/build-artifacts/02:22:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3870/artifact/build-artifacts/02:22:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.000
1:36.230
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 44.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.805
And Tails is fooled to think it is running version 6.0~testoverlayfs 1.087
And the signing key used by the Upgrader is outdated 1.969
But a current signing key is available on our website 0.000
When the network is plugged 2.002
And Tor is ready 27.317
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 17.965
After features/support/hooks.rb:330 1.936
After features/support/hooks.rb:100 0.000