Project Number Date
test_Tails_ISO_21348-migrate-away-from-sysadmin-team-container-images 5 18 Jun 2026, 17:33

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:16.845 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:7.952
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.142
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 13.706
When I start Tails from USB drive "old" with network unplugged 49.728
Then the boot device has safe access rights 2.740
And Tails is running from USB drive "old" 0.188
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.900
After features/support/hooks.rb:108 0.032
Tags: @product
1:32.620
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.030
Given a computer 0.135
And I start Tails from USB drive "old" with network unplugged and I login 56.621
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 25.948
And I take note of which tps features are available 4.572
Then a Tails persistence partition exists on USB drive "old" 0.580
And I shutdown Tails and wait for the computer to power off 4.517
After features/support/hooks.rb:339 0.260
After features/support/hooks.rb:108 0.018
Tags: @product
1:43.065
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.302
Then Tails is running from USB drive "old" 0.245
And all tps features are active 5.462
When I write some files expected to persist 1.497
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 2.008
And I take note of which tps features are available 3.897
And I shutdown Tails and wait for the computer to power off 8.527
# 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" 12.370
After features/support/hooks.rb:339 0.299
After features/support/hooks.rb:108 0.016
Tags: @product
2:12.618
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.189
And I log in to a new session 12.554
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.850
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.159
Then the running Tails is installed on USB drive "to_upgrade" 16.335
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.077
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.007
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.114
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.306
Then all tps features from the old Tails version are active 1.134
And Tails is running from USB drive "to_upgrade" 0.292
And the boot device has safe access rights 2.739
And the expected persistent files created with the old Tails version are present in the filesystem 1.217
And all persistent directories from the old Tails version have safe access rights 2.203
After features/support/hooks.rb:339 0.868
After features/support/hooks.rb:108 0.031
Tags: @product @automatic_upgrade
4:2.756
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.027
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.379
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.016
And Tor is ready 13.363
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.924
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.419
Given I shutdown Tails and wait for the computer to power off 10.188
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.672
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 6.088
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.218
# 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.223
When the network is plugged 0.014
And Tor is ready 9.909
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.776
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.114
Given I shutdown Tails and wait for the computer to power off 6.973
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.671
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.444
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.017
And Tor is ready 10.005
Then the Upgrader considers the system as up-to-date 10.560
# 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 4.285
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:339 0.748
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
20.824
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.544
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.641
After features/support/hooks.rb:339 0.900
After features/support/hooks.rb:108 0.000