Project Number Date
test_Tails_ISO_issue-template-stop-tracking-oldstable 2 01 Oct 2026, 17:38

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 12:32.563 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:13.022
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 13.846
When I start Tails from USB drive "old" with network unplugged 54.298
Then the boot device has safe access rights 2.942
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:339 3.801
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.171
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 51.071
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 24.390
And I take note of which tps features are available 6.641
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 4.108
After features/support/hooks.rb:339 0.290
After features/support/hooks.rb:108 0.012
Tags: @product
1:42.431
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.336
Then Tails is running from USB drive "old" 0.221
And all tps features are active 7.971
When I write some files expected to persist 1.286
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.285
And all persistent directories from the old Tails version have safe access rights 1.889
And I take note of which tps features are available 7.568
And I shutdown Tails and wait for the computer to power off 4.287
# 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" 13.294
After features/support/hooks.rb:339 0.376
After features/support/hooks.rb:108 0.008
Tags: @product
2:16.099
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 9.152
And I log in to a new session 12.578
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.749
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.431
Then the running Tails is installed on USB drive "to_upgrade" 19.715
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 2.579
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.186
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:6.185
Then all tps features from the old Tails version are active 1.151
And Tails is running from USB drive "to_upgrade" 0.180
And the boot device has safe access rights 2.170
And the expected persistent files created with the old Tails version are present in the filesystem 0.851
And all persistent directories from the old Tails version have safe access rights 1.546
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:55.221
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 21.640
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.403
When the network is plugged 0.029
And Tor is ready 12.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.030
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.846
Given I shutdown Tails and wait for the computer to power off 5.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.149
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.105
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.195
When the network is plugged 0.032
And Tor is ready 12.310
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.417
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.698
Given I shutdown Tails and wait for the computer to power off 4.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.530
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.919
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.031
And Tor is ready 10.604
Then the Upgrader considers the system as up-to-date 0.105
# 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.802
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:339 0.654
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
46.430
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 35.106
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.048
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 9.982
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.978
After features/support/hooks.rb:339 0.930
After features/support/hooks.rb:108 0.000