Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 8 12 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 10:53.932 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:17.188
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.670
When I start Tails from USB drive "old" with network unplugged 59.910
Then the boot device has safe access rights 1.960
And Tails is running from USB drive "old" 0.175
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.162
And I unplug USB drive "old" 0.106
After features/support/hooks.rb:339 1.601
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.869
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 46.078
Then Tails is running from USB drive "old" 0.195
And I create a persistent partition 22.351
And I take note of which tps features are available 6.116
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 2.539
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.392
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.367
Then Tails is running from USB drive "old" 0.168
And all tps features are active 6.623
When I write some files expected to persist 1.047
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.113
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.450
And I take note of which tps features are available 6.213
And I shutdown Tails and wait for the computer to power off 3.879
# 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.152
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.016
Tags: @product
2:12.052
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.329
And I log in to a new session 11.677
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.745
And I plug USB drive "to_upgrade" 2.193
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.977
Then the running Tails is installed on USB drive "to_upgrade" 17.893
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.785
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.955
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.199
Then all tps features from the old Tails version are active 1.042
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 2.023
And the expected persistent files created with the old Tails version are present in the filesystem 0.809
And all persistent directories from the old Tails version have safe access rights 1.597
After features/support/hooks.rb:339 0.673
After features/support/hooks.rb:108 0.006
3:16.325
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.018
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.026
And Tor is ready 12.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.393
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.241
Given I shutdown Tails and wait for the computer to power off 5.259
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.381
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.028
And the file system changes introduced in version 6.2~testoverlayfs are present 0.148
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.109
# 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.146
When the network is plugged 0.023
And Tor is ready 10.088
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.290
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.566
Given I shutdown Tails and wait for the computer to power off 2.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.170
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.300
And the file system changes introduced in version 6.3~testoverlayfs are present 0.337
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.098
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.039
And Tor is ready 10.022
Then the Upgrader considers the system as up-to-date 0.058
# 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 2.928
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.296
After features/support/hooks.rb:339 0.962
After features/support/hooks.rb:108 0.009
17.148
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.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
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.060
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 7.806
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.441
After features/support/hooks.rb:339 0.533
After features/support/hooks.rb:108 0.000