Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 10 14 Oct 2026, 05:52

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:47.245 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:1.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.244
When I start Tails from USB drive "old" with network unplugged 44.932
Then the boot device has safe access rights 1.748
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.026
And udev-watchdog is monitoring the correct device 0.135
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 3.460
After features/support/hooks.rb:108 0.031
Tags: @product
1:18.814
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 47.478
Then Tails is running from USB drive "old" 0.204
And I create a persistent partition 22.197
And I take note of which tps features are available 5.825
Then a Tails persistence partition exists on USB drive "old" 0.465
And I shutdown Tails and wait for the computer to power off 2.574
After features/support/hooks.rb:339 0.531
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.394
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.461
Then Tails is running from USB drive "old" 0.166
And all tps features are active 8.138
When I write some files expected to persist 0.968
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.267
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 5.739
And I shutdown Tails and wait for the computer to power off 2.501
# 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.411
After features/support/hooks.rb:339 0.411
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.304
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 without a persistent partition and stopped at Tails Greeter's login screen 8.191
And I log in to a new session 11.148
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.659
And I plug USB drive "to_upgrade" 2.192
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.352
Then the running Tails is installed on USB drive "to_upgrade" 17.519
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.639
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.629
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.792
Then all tps features from the old Tails version are active 1.107
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 1.977
And the expected persistent files created with the old Tails version are present in the filesystem 0.909
And all persistent directories from the old Tails version have safe access rights 1.554
After features/support/hooks.rb:339 0.607
After features/support/hooks.rb:108 0.004
Tags: @product @automatic_upgrade
3:22.688
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.886
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.164
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.140
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.264
When the network is plugged 0.032
And Tor is ready 12.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.930
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.710
Given I shutdown Tails and wait for the computer to power off 5.434
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.345
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.463
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.098
# 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.171
When the network is plugged 0.027
And Tor is ready 10.228
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.291
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.712
Given I shutdown Tails and wait for the computer to power off 2.535
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.281
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.054
And the file system changes introduced in version 6.3~testoverlayfs are present 0.320
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.034
And Tor is ready 10.237
Then the Upgrader considers the system as up-to-date 0.087
# 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.213
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.333
After features/support/hooks.rb:339 0.638
After features/support/hooks.rb:108 0.051
Tags: @product @automatic_upgrade
18.827
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.511
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.555
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.419
After features/support/hooks.rb:339 0.848
After features/support/hooks.rb:108 0.000