Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 1 06 Oct 2026, 12:00

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:17.004 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:8.528
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.321
When I start Tails from USB drive "old" with network unplugged 51.147
Then the boot device has safe access rights 2.254
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:339 3.530
After features/support/hooks.rb:108 0.019
Tags: @product
1:23.819
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 48.794
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 23.743
And I take note of which tps features are available 6.624
Then a Tails persistence partition exists on USB drive "old" 0.482
And I shutdown Tails and wait for the computer to power off 3.863
After features/support/hooks.rb:339 0.556
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.746
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.542
Then Tails is running from USB drive "old" 0.161
And all tps features are active 6.801
When I write some files expected to persist 1.181
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 1.872
And I take note of which tps features are available 6.109
And I shutdown Tails and wait for the computer to power off 2.561
# 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.879
After features/support/hooks.rb:339 0.590
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.046
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.440
And I log in to a new session 12.599
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.644
And I plug USB drive "to_upgrade" 2.294
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.270
Then the running Tails is installed on USB drive "to_upgrade" 18.561
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.805
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.103
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.606
Then all tps features from the old Tails version are active 1.253
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.077
And the expected persistent files created with the old Tails version are present in the filesystem 1.076
And all persistent directories from the old Tails version have safe access rights 1.776
After features/support/hooks.rb:339 0.635
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:30.544
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.118
And no SquashFS delta is installed 0.074
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.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.032
And Tor is ready 12.834
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.299
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.917
Given I shutdown Tails and wait for the computer to power off 5.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.557
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.619
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.118
# 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.185
When the network is plugged 0.041
And Tor is ready 10.398
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.379
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.869
Given I shutdown Tails and wait for the computer to power off 2.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.551
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 8.429
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.037
And Tor is ready 10.215
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.491
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.395
After features/support/hooks.rb:339 1.118
After features/support/hooks.rb:108 0.069
Tags: @product @automatic_upgrade
18.216
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.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 8.137
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.580
After features/support/hooks.rb:339 0.984
After features/support/hooks.rb:108 0.000