Project Number Date
test_Tails_ISO_21348-migrate-away-from-sysadmin-team-container-images 6 19 Jun 2026, 17:28

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:39.763 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:12.225
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.125
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.372
When I start Tails from USB drive "old" with network unplugged 54.520
Then the boot device has safe access rights 2.518
And Tails is running from USB drive "old" 0.205
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 3.410
After features/support/hooks.rb:108 0.032
Tags: @product
1:27.151
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.145
And I start Tails from USB drive "old" with network unplugged and I login 52.371
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 23.277
And I take note of which tps features are available 3.752
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 6.885
After features/support/hooks.rb:339 0.180
After features/support/hooks.rb:108 0.024
Tags: @product
1:32.737
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.449
Then Tails is running from USB drive "old" 0.224
And all tps features are active 4.669
When I write some files expected to persist 1.179
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.137
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 1.700
And I take note of which tps features are available 3.761
And I shutdown Tails and wait for the computer to power off 4.369
# 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.816
After features/support/hooks.rb:339 0.625
After features/support/hooks.rb:108 0.017
Tags: @product
2:10.538
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.173
And I log in to a new session 12.604
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.769
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.835
Then the running Tails is installed on USB drive "to_upgrade" 14.667
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:339 2.070
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.892
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.154
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.301
Then all tps features from the old Tails version are active 0.905
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.456
And the expected persistent files created with the old Tails version are present in the filesystem 1.045
And all persistent directories from the old Tails version have safe access rights 1.801
After features/support/hooks.rb:339 0.935
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
3:46.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.549
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.015
And Tor is ready 12.226
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.672
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.135
Given I shutdown Tails and wait for the computer to power off 6.914
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.431
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.864
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.227
When the network is plugged 0.019
And Tor is ready 10.613
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.943
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.716
Given I shutdown Tails and wait for the computer to power off 8.064
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.139
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.878
And the file system changes introduced in version 6.3~testoverlayfs are present 0.357
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.018
And Tor is ready 9.892
Then the Upgrader considers the system as up-to-date 10.503
# 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.270
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.345
After features/support/hooks.rb:339 0.655
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
19.463
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.530
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.926
After features/support/hooks.rb:339 0.768
After features/support/hooks.rb:108 0.000