Project Number Date
test_Tails_ISO_21319-thunderbird-153 6 27 Oct 2026, 17:13

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:19.110 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:15.022
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.002
Steps
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 16.982
When I start Tails from USB drive "old" with network unplugged 56.893
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.181 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 01:09:50)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21319-thunderbird-153/6/artifact/build-artifacts/01:09:50_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21319-thunderbird-153/6/artifact/build-artifacts/01:09:50_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21319-thunderbird-153/6/artifact/build-artifacts/01:09:50_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21319-thunderbird-153/6/artifact/build-artifacts/01:09:50_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:108 0.007
Tags: @product
1:26.944
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.130
And I start Tails from USB drive "old" with network unplugged and I login 50.354
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 25.051
And I take note of which tps features are available 7.965
Then a Tails persistence partition exists on USB drive "old" 0.614
And I shutdown Tails and wait for the computer to power off 2.621
After features/support/hooks.rb:339 0.427
After features/support/hooks.rb:108 0.009
Tags: @product
1:42.635
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.105
Then Tails is running from USB drive "old" 0.245
And all tps features are active 9.505
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.182
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 1.772
And I take note of which tps features are available 7.982
And I shutdown Tails and wait for the computer to power off 4.131
# 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.088
After features/support/hooks.rb:339 0.186
After features/support/hooks.rb:108 0.007
Tags: @product
2:16.540
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 without a persistent partition and stopped at Tails Greeter's login screen 8.968
And I log in to a new session 11.786
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.088
And I plug USB drive "to_upgrade" 2.286
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.521
Then the running Tails is installed on USB drive "to_upgrade" 20.617
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 3.571
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.483
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.341
Then all tps features from the old Tails version are active 1.167
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 2.258
And the expected persistent files created with the old Tails version are present in the filesystem 1.128
And all persistent directories from the old Tails version have safe access rights 2.210
After features/support/hooks.rb:339 0.775
After features/support/hooks.rb:108 0.046
Tags: @product @automatic_upgrade
3:46.840
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 8.283
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.561
When the network is plugged 0.049
And Tor is ready 13.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.983
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.788
Given I shutdown Tails and wait for the computer to power off 5.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.480
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.717
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.174
When the network is plugged 0.029
And Tor is ready 10.746
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.336
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.837
Given I shutdown Tails and wait for the computer to power off 4.095
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.173
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 8.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.297
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.173
When the network is plugged 0.023
And Tor is ready 10.229
Then the Upgrader considers the system as up-to-date 10.525
# 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 3.734
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.308
After features/support/hooks.rb:339 0.988
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
35.642
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 21.561
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
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.044
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 13.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.305
After features/support/hooks.rb:339 0.507
After features/support/hooks.rb:108 0.000