Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 6 10 Oct 2026, 06:02

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:54.702 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:9.318
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
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.242
When I start Tails from USB drive "old" with network unplugged 52.557
Then the boot device has safe access rights 1.860
And Tails is running from USB drive "old" 0.178
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.148
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.744
After features/support/hooks.rb:108 0.028
Tags: @product
1:20.422
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 46.577
Then Tails is running from USB drive "old" 0.207
And I create a persistent partition 23.254
And I take note of which tps features are available 5.918
Then a Tails persistence partition exists on USB drive "old" 0.461
And I shutdown Tails and wait for the computer to power off 3.923
After features/support/hooks.rb:339 0.429
After features/support/hooks.rb:108 0.007
Tags: @product
1:29.345
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.649
Then Tails is running from USB drive "old" 0.216
And all tps features are active 6.794
When I write some files expected to persist 0.969
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.108
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 1.551
And I take note of which tps features are available 5.879
And I shutdown Tails and wait for the computer to power off 2.531
# 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.182
After features/support/hooks.rb:339 0.461
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.647
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.566
And I log in to a new session 10.992
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.599
And I plug USB drive "to_upgrade" 2.288
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.652
Then the running Tails is installed on USB drive "to_upgrade" 17.296
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.792
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.457
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.341
Then all tps features from the old Tails version are active 0.931
And Tails is running from USB drive "to_upgrade" 0.184
And the boot device has safe access rights 1.967
And the expected persistent files created with the old Tails version are present in the filesystem 0.739
And all persistent directories from the old Tails version have safe access rights 1.220
After features/support/hooks.rb:339 0.708
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:22.994
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.185
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.167
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.024
And Tor is ready 13.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.831
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.259
Given I shutdown Tails and wait for the computer to power off 5.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.071
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.951
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.077
# 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.162
When the network is plugged 0.034
And Tor is ready 10.026
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.842
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.435
Given I shutdown Tails and wait for the computer to power off 2.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.973
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 7.686
And the file system changes introduced in version 6.3~testoverlayfs are present 0.289
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.138
When the network is plugged 0.031
And Tor is ready 9.933
Then the Upgrader considers the system as up-to-date 0.086
# 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.403
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 0.916
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
17.515
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.789
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 9.120
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.278
After features/support/hooks.rb:339 0.684
After features/support/hooks.rb:108 0.000