Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 2 06 Oct 2026, 12:28

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:43.067 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:12.311
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.678
When I start Tails from USB drive "old" with network unplugged 54.175
Then the boot device has safe access rights 2.587
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 1.200
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.511
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.120
And I start Tails from USB drive "old" with network unplugged and I login 50.528
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 24.935
And I take note of which tps features are available 7.221
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 3.901
After features/support/hooks.rb:339 0.325
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.311
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.808
Then Tails is running from USB drive "old" 0.266
And all tps features are active 8.227
When I write some files expected to persist 1.307
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.292
And all persistent directories from the old Tails version have safe access rights 1.938
And I take note of which tps features are available 6.948
And I shutdown Tails and wait for the computer to power off 4.066
# 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" 12.151
After features/support/hooks.rb:339 0.492
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.363
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.349
And I log in to a new session 11.965
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.719
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.778
Then the running Tails is installed on USB drive "to_upgrade" 19.056
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 3.735
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.338
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.118
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.907
Then all tps features from the old Tails version are active 1.305
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.550
And the expected persistent files created with the old Tails version are present in the filesystem 1.256
And all persistent directories from the old Tails version have safe access rights 1.982
After features/support/hooks.rb:339 0.945
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:35.079
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 8.445
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.269
When the network is plugged 0.025
And Tor is ready 13.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.970
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.824
Given I shutdown Tails and wait for the computer to power off 5.386
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.213
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 7.904
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.165
When the network is plugged 0.034
And Tor is ready 10.699
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.354
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.122
Given I shutdown Tails and wait for the computer to power off 2.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.630
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.173
And the file system changes introduced in version 6.3~testoverlayfs are present 0.302
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.080
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.023
And Tor is ready 10.414
Then the Upgrader considers the system as up-to-date 0.090
# 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.193
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:339 1.256
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
21.151
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 8.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 10.659
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.033
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.000