Project Number Date
test_Tails_ISO_21352-remove-haveged-and-rngd 2 15 Jul 2026, 08:35

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:18.163 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.058
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.048
When I start Tails from USB drive "old" with network unplugged 57.450
Then the boot device has safe access rights 2.742
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.503
After features/support/hooks.rb:108 0.061
Tags: @product
1:34.810
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 56.330
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 26.133
And I take note of which tps features are available 4.736
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 6.757
After features/support/hooks.rb:339 0.579
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.517
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.007
Then Tails is running from USB drive "old" 0.298
And all tps features are active 5.391
When I write some files expected to persist 1.445
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.334
And all persistent directories from the old Tails version have safe access rights 2.104
And I take note of which tps features are available 3.639
And I shutdown Tails and wait for the computer to power off 4.195
# 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.863
After features/support/hooks.rb:339 0.376
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.686
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.965
And I log in to a new session 13.925
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.695
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.105
Then the running Tails is installed on USB drive "to_upgrade" 15.502
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 0.604
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.713
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.879
Then all tps features from the old Tails version are active 0.989
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.410
And the expected persistent files created with the old Tails version are present in the filesystem 1.155
And all persistent directories from the old Tails version have safe access rights 1.978
After features/support/hooks.rb:339 0.629
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
4:3.004
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.621
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 0.030
And Tor is ready 13.281
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.141
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.655
Given I shutdown Tails and wait for the computer to power off 9.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.363
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.044
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.193
When the network is plugged 0.014
And Tor is ready 11.628
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.275
Given I shutdown Tails and wait for the computer to power off 8.222
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.174
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.236
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.016
And Tor is ready 11.204
Then the Upgrader considers the system as up-to-date 10.573
# 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.397
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.627
After features/support/hooks.rb:339 1.013
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
21.370
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.898
After features/support/hooks.rb:339 0.953
After features/support/hooks.rb:108 0.000