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

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 80 1 6 0 0 87 6 1 7 12:10.024 Failed
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:19.816
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.410
When I start Tails from USB drive "old" with network unplugged 1:5.308
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:238:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:339 5.240 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 01:02:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21352-remove-haveged-and-rngd/4/artifact/build-artifacts/01:02:51_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21352-remove-haveged-and-rngd/4/artifact/build-artifacts/01:02:51_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21352-remove-haveged-and-rngd/4/artifact/build-artifacts/01:02:51_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21352-remove-haveged-and-rngd/4/artifact/build-artifacts/01:02:51_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:108 0.022
Tags: @product
1:33.006
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 54.985
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 24.767
And I take note of which tps features are available 3.980
Then a Tails persistence partition exists on USB drive "old" 0.725
And I shutdown Tails and wait for the computer to power off 8.246
After features/support/hooks.rb:339 0.365
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.313
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.220
Then Tails is running from USB drive "old" 0.237
And all tps features are active 4.699
When I write some files expected to persist 1.157
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 2.121
And I take note of which tps features are available 3.974
And I shutdown Tails and wait for the computer to power off 7.907
# 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.387
After features/support/hooks.rb:339 0.518
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.419
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.411
And I log in to a new session 13.656
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.799
And I plug USB drive "to_upgrade" 2.250
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.267
Then the running Tails is installed on USB drive "to_upgrade" 15.742
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 2.322
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.661
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.013
Then all tps features from the old Tails version are active 0.934
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.443
And the expected persistent files created with the old Tails version are present in the filesystem 1.124
And all persistent directories from the old Tails version have safe access rights 1.868
After features/support/hooks.rb:339 0.543
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:56.091
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.883
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
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.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.014
And Tor is ready 12.794
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.218
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.792
Given I shutdown Tails and wait for the computer to power off 9.465
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.026
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.503
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.186
When the network is plugged 0.014
And Tor is ready 10.991
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.554
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.689
Given I shutdown Tails and wait for the computer to power off 7.951
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.913
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.016
And Tor is ready 9.688
Then the Upgrader considers the system as up-to-date 10.559
# 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.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 0.874
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.714
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.163
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.283
After features/support/hooks.rb:339 1.018
After features/support/hooks.rb:108 0.000