Project Number Date
test_Tails_ISO_issue-template-stop-tracking-oldstable 3 02 Oct 2026, 05:56

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:45.644 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:2.620
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.465
When I start Tails from USB drive "old" with network unplugged 45.339
Then the boot device has safe access rights 2.189
And Tails is running from USB drive "old" 0.191
And there is no persistence partition on USB drive "old" 0.029
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.150
And I unplug USB drive "old" 0.106
After features/support/hooks.rb:339 3.469
After features/support/hooks.rb:108 0.009
Tags: @product
1:19.738
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 46.578
Then Tails is running from USB drive "old" 0.189
And I create a persistent partition 22.113
And I take note of which tps features are available 6.067
Then a Tails persistence partition exists on USB drive "old" 0.511
And I shutdown Tails and wait for the computer to power off 4.200
After features/support/hooks.rb:339 0.557
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.744
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.270
Then Tails is running from USB drive "old" 0.256
And all tps features are active 6.745
When I write some files expected to persist 0.955
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.109
And all persistence configuration files have safe access rights 0.224
And all persistent directories from the old Tails version have safe access rights 1.394
And I take note of which tps features are available 5.574
And I shutdown Tails and wait for the computer to power off 3.900
# 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.227
After features/support/hooks.rb:339 0.526
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.899
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.314
And I log in to a new session 10.267
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.601
And I plug USB drive "to_upgrade" 2.188
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.833
Then the running Tails is installed on USB drive "to_upgrade" 17.445
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 1.739
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.370
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.998
Then all tps features from the old Tails version are active 0.971
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 1.832
And the expected persistent files created with the old Tails version are present in the filesystem 0.887
And all persistent directories from the old Tails version have safe access rights 1.360
After features/support/hooks.rb:339 0.816
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
3:20.444
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 7.999
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.291
When the network is plugged 0.027
And Tor is ready 11.402
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.845
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.733
Given I shutdown Tails and wait for the computer to power off 5.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.184
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.423
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.153
When the network is plugged 0.039
And Tor is ready 10.219
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.310
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.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.880
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.142
When the network is plugged 0.035
And Tor is ready 10.322
Then the Upgrader considers the system as up-to-date 0.103
# 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.038
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.275
After features/support/hooks.rb:339 0.835
After features/support/hooks.rb:108 0.058
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.854
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.843
After features/support/hooks.rb:339 0.819
After features/support/hooks.rb:108 0.000