Project Number Date
test_Tails_ISO_21352-remove-haveged-and-rngd 1 14 Jul 2026, 21:43

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:31.073 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:18.103
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.586
When I start Tails from USB drive "old" with network unplugged 59.920
Then the boot device has safe access rights 2.847
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 1.622
After features/support/hooks.rb:108 0.009
Tags: @product
1:35.149
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 56.736
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 25.450
And I take note of which tps features are available 4.753
Then a Tails persistence partition exists on USB drive "old" 0.698
And I shutdown Tails and wait for the computer to power off 7.149
After features/support/hooks.rb:339 0.241
After features/support/hooks.rb:108 0.007
Tags: @product
1:43.005
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.153
Then Tails is running from USB drive "old" 0.261
And all tps features are active 5.563
When I write some files expected to persist 1.383
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.294
And all persistent directories from the old Tails version have safe access rights 2.153
And I take note of which tps features are available 4.099
And I shutdown Tails and wait for the computer to power off 8.033
# 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.803
After features/support/hooks.rb:339 0.366
After features/support/hooks.rb:108 0.009
Tags: @product
2:13.237
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.020
And I log in to a new session 13.522
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.154
Then the running Tails is installed on USB drive "to_upgrade" 16.290
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.222
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.699
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.307
Then all tps features from the old Tails version are active 0.983
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.708
And the expected persistent files created with the old Tails version are present in the filesystem 1.179
And all persistent directories from the old Tails version have safe access rights 2.256
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
4:6.405
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.800
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.015
And Tor is ready 13.160
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.639
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.122
Given I shutdown Tails and wait for the computer to power off 9.742
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.304
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.970
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.209
When the network is plugged 0.016
And Tor is ready 9.883
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.098
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.687
Given I shutdown Tails and wait for the computer to power off 8.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.472
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.970
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.205
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.014
And Tor is ready 11.840
Then the Upgrader considers the system as up-to-date 10.546
# 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.585
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.452
After features/support/hooks.rb:339 1.122
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
20.472
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.387
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.610
After features/support/hooks.rb:339 0.822
After features/support/hooks.rb:108 0.000