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

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.582 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:16.233
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 13.178
When I start Tails from USB drive "old" with network unplugged 58.153
Then the boot device has safe access rights 3.035
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 3.925
After features/support/hooks.rb:108 0.079
Tags: @product
1:33.441
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 54.887
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 24.723
And I take note of which tps features are available 4.057
Then a Tails persistence partition exists on USB drive "old" 0.511
And I shutdown Tails and wait for the computer to power off 8.810
After features/support/hooks.rb:339 0.432
After features/support/hooks.rb:108 0.043
Tags: @product
1:38.204
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.145
Then Tails is running from USB drive "old" 0.301
And all tps features are active 4.965
When I write some files expected to persist 1.411
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 2.073
And I take note of which tps features are available 4.670
And I shutdown Tails and wait for the computer to power off 4.577
# 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.314
After features/support/hooks.rb:339 0.254
After features/support/hooks.rb:108 0.021
Tags: @product
2:11.929
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.419
And I log in to a new session 12.162
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.967
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.994
Then the running Tails is installed on USB drive "to_upgrade" 15.856
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:339 1.994
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.091
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.566
Then all tps features from the old Tails version are active 1.075
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 2.591
And the expected persistent files created with the old Tails version are present in the filesystem 1.243
And all persistent directories from the old Tails version have safe access rights 2.117
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
4:0.516
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.454
And no SquashFS delta is installed 0.065
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.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.042
And Tor is ready 12.792
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.496
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.391
Given I shutdown Tails and wait for the computer to power off 9.935
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.272
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.806
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.214
# 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.208
When the network is plugged 0.021
And Tor is ready 9.807
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.751
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.327
Given I shutdown Tails and wait for the computer to power off 7.159
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.921
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.551
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.018
And Tor is ready 9.707
Then the Upgrader considers the system as up-to-date 10.642
# 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.294
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:339 0.883
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
21.164
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.753
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.359
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.546
After features/support/hooks.rb:339 0.554
After features/support/hooks.rb:108 0.000