Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 5 09 Oct 2026, 05:57

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 11:14.994 Passed
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
1:18.863
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.501
When I start Tails from USB drive "old" with network unplugged 1:1.849
Then the boot device has safe access rights 1.845
And Tails is running from USB drive "old" 0.171
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.150
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 1.530
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.437
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 47.380
Then Tails is running from USB drive "old" 0.181
And I create a persistent partition 22.701
And I take note of which tps features are available 6.043
Then a Tails persistence partition exists on USB drive "old" 0.479
And I shutdown Tails and wait for the computer to power off 2.570
After features/support/hooks.rb:339 0.411
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.191
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.122
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.182
Then Tails is running from USB drive "old" 0.226
And all tps features are active 8.444
When I write some files expected to persist 1.081
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.203
And all persistent directories from the old Tails version have safe access rights 1.504
And I take note of which tps features are available 6.085
And I shutdown Tails and wait for the computer to power off 2.556
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.602
After features/support/hooks.rb:339 0.171
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.891
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.352
And I log in to a new session 11.642
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.658
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.919
Then the running Tails is installed on USB drive "to_upgrade" 18.863
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.943
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.195
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.044
Then all tps features from the old Tails version are active 1.130
And Tails is running from USB drive "to_upgrade" 0.188
And the boot device has safe access rights 2.109
And the expected persistent files created with the old Tails version are present in the filesystem 0.881
And all persistent directories from the old Tails version have safe access rights 1.766
After features/support/hooks.rb:339 0.447
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:23.535
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.955
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.037
And Tor is ready 13.145
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.315
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.380
Given I shutdown Tails and wait for the computer to power off 5.362
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.601
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.576
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.169
When the network is plugged 0.026
And Tor is ready 10.894
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.315
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.627
Given I shutdown Tails and wait for the computer to power off 2.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.009
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.621
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.077
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.029
And Tor is ready 10.270
Then the Upgrader considers the system as up-to-date 0.086
# 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 3.168
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.366
After features/support/hooks.rb:339 0.827
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.879
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.951
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.984
After features/support/hooks.rb:339 0.818
After features/support/hooks.rb:108 0.000