Project Number Date
test_Tails_ISO_21348-migrate-away-from-sysadmin-team-container-images 7 20 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:50.059 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:13.000
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.303
When I start Tails from USB drive "old" with network unplugged 55.272
Then the boot device has safe access rights 2.622
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:339 1.385
After features/support/hooks.rb:108 0.016
Tags: @product
1:28.929
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login 52.054
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 23.723
And I take note of which tps features are available 4.061
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 8.213
After features/support/hooks.rb:339 0.414
After features/support/hooks.rb:108 0.016
Tags: @product
1:36.615
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.116
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.126
Then Tails is running from USB drive "old" 0.258
And all tps features are active 4.902
When I write some files expected to persist 1.150
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 1.972
And I take note of which tps features are available 3.783
And I shutdown Tails and wait for the computer to power off 6.905
# 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.883
After features/support/hooks.rb:339 0.208
After features/support/hooks.rb:108 0.017
Tags: @product
2:12.437
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 9.133
And I log in to a new session 12.982
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.835
And I plug USB drive "to_upgrade" 2.250
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.326
Then the running Tails is installed on USB drive "to_upgrade" 15.646
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.398
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.746
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.157
Then all tps features from the old Tails version are active 0.956
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.411
And the expected persistent files created with the old Tails version are present in the filesystem 1.015
And all persistent directories from the old Tails version have safe access rights 1.883
After features/support/hooks.rb:339 0.508
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:48.605
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 8.299
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.018
And Tor is ready 13.267
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.692
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.041
Given I shutdown Tails and wait for the computer to power off 9.585
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.687
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.839
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
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.142
# 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.202
When the network is plugged 0.017
And Tor is ready 9.829
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.673
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.654
Given I shutdown Tails and wait for the computer to power off 8.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.958
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 4.921
And the file system changes introduced in version 6.3~testoverlayfs are present 0.402
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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.018
And Tor is ready 9.439
Then the Upgrader considers the system as up-to-date 10.484
# 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.192
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:339 0.784
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
20.724
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 7.461
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
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.039
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.310
After features/support/hooks.rb:339 1.015
After features/support/hooks.rb:108 0.000