Project Number Date
test_Tails_ISO_21352-remove-haveged-and-rngd 3 15 Jul 2026, 16:07

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:1.293 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.045
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.610
When I start Tails from USB drive "old" with network unplugged 53.917
Then the boot device has safe access rights 2.754
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.527
After features/support/hooks.rb:108 0.045
Tags: @product
1:26.504
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 53.670
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 24.025
And I take note of which tps features are available 3.813
Then a Tails persistence partition exists on USB drive "old" 0.501
And I shutdown Tails and wait for the computer to power off 4.200
After features/support/hooks.rb:339 0.358
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.574
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.341
Then Tails is running from USB drive "old" 0.273
And all tps features are active 5.481
When I write some files expected to persist 1.455
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 2.067
And I take note of which tps features are available 4.116
And I shutdown Tails and wait for the computer to power off 6.951
# 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.358
After features/support/hooks.rb:339 0.254
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.510
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 8.353
And I log in to a new session 12.001
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.833
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.992
Then the running Tails is installed on USB drive "to_upgrade" 15.554
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 2.162
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.715
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:5.432
Then all tps features from the old Tails version are active 1.091
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.733
And the expected persistent files created with the old Tails version are present in the filesystem 1.103
And all persistent directories from the old Tails version have safe access rights 2.086
After features/support/hooks.rb:339 0.552
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:59.471
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.198
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.310
When the network is plugged 0.013
And Tor is ready 12.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.253
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.465
Given I shutdown Tails and wait for the computer to power off 10.894
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.960
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 5.007
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.219
When the network is plugged 0.019
And Tor is ready 10.012
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.555
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.805
Given I shutdown Tails and wait for the computer to power off 8.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.138
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.790
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.019
And Tor is ready 11.170
Then the Upgrader considers the system as up-to-date 10.625
# 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.706
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.444
After features/support/hooks.rb:339 1.081
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.471
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
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.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.458
After features/support/hooks.rb:339 0.702
After features/support/hooks.rb:108 0.000