Project Number Date
test_Tails_ISO_stable 5759 05 Jul 2025, 14:17

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 85 1 1 0 0 87 6 1 7 25:42.535 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
2:47.607
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Given a computer 0.297
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 41.729
When I start Tails from USB drive "old" with network unplugged 2:0.209
Then the boot device has safe access rights 3.128
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.258
After features/support/hooks.rb:330 4.029
After features/support/hooks.rb:100 0.011
Tags: @product
3:0.905
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:57.637
Then Tails is running from USB drive "old" 0.595
And I create a persistent partition 48.707
And I take note of which tps features are available 3.963
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.964
After features/support/hooks.rb:330 2.016
After features/support/hooks.rb:100 0.095
Tags: @product
4:7.383
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.120
Given a computer 0.857
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:7.075
Then Tails is running from USB drive "old" 0.643
And all tps features are active 2.009
When I write some files expected to persist 1.806
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.462
And all persistent directories from the old Tails version have safe access rights 3.759
And I take note of which tps features are available 1.026
And I shutdown Tails and wait for the computer to power off 8.177
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 41.310
After features/support/hooks.rb:330 0.228
After features/support/hooks.rb:100 0.016
Tags: @product
3:3.638
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.996
And I log in to a new session 29.406
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.391
And I plug USB drive "to_upgrade" 2.702
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.560
Then the running Tails is installed on USB drive "to_upgrade" 28.168
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 3.520
After features/support/hooks.rb:100 0.000
Tags: @product
3:14.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.310
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:56.446
Then all tps features from the old Tails version are active 2.437
And Tails is running from USB drive "to_upgrade" 0.577
And the boot device has safe access rights 8.064
And the expected persistent files created with the old Tails version are present in the filesystem 4.058
And all persistent directories from the old Tails version have safe access rights 2.878
After features/support/hooks.rb:330 1.860
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:59.244
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.491
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.508
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.423
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.071
And Tor is ready 24.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.228
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.149
Given I shutdown Tails and wait for the computer to power off 10.007
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:52.673
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.398
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.326
# 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.403
When the network is plugged 0.079
And Tor is ready 30.449
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.656
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.141
Given I shutdown Tails and wait for the computer to power off 7.810
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:44.176
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 4.119
And the file system changes introduced in version 6.3~testoverlayfs are present 1.887
And only the 6.3~testoverlayfs SquashFS delta is installed 0.132
# 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.577
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.882
When the network is plugged 0.123
And Tor is ready 24.489
Then the Upgrader considers the system as up-to-date 0.393
# 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 20.915
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.608
After features/support/hooks.rb:330 0.713
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
28.984
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.012
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.555
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the signing key used by the Upgrader is outdated 0.094
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 11.145
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:133:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:330 6.768 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:17:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5759/artifact/build-artifacts/02:17:05_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5759/artifact/build-artifacts/02:17:05_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5759/artifact/build-artifacts/02:17:05_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5759/artifact/build-artifacts/02:17:05_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000