Project Number Date
test_Tails_ISO_stable 5730 23 Jun 2025, 11:42

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 79 1 7 0 0 87 6 1 7 36:55.222 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
4:16.403
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.170
And I write an old version of the Tails USB image to disk "old" 1:2.366
When I start Tails from USB drive "old" with network unplugged 3:1.422
Then the boot device has safe access rights 9.872
And Tails is running from USB drive "old" 0.428
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.399
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:330 5.131
After features/support/hooks.rb:100 0.574
Tags: @product
4:1.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.534
Given a computer 5.044
And I start Tails from USB drive "old" with network unplugged and I login 2:28.411
Then Tails is running from USB drive "old" 0.654
And I create a persistent partition 1:5.802
And I take note of which tps features are available 7.767
Then a Tails persistence partition exists on USB drive "old" 2.153
And I shutdown Tails and wait for the computer to power off 12.015
After features/support/hooks.rb:330 1.626
After features/support/hooks.rb:100 0.060
Tags: @product
5:52.927
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.044
Given a computer 1.407
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:29.263
Then Tails is running from USB drive "old" 0.968
And all tps features are active 6.624
When I write some files expected to persist 7.839
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 2.883
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 8.484
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 54.248
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.010
Tags: @product
4:32.690
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 21.849
And I log in to a new session 38.017
And I clone USB drive "old" to a new USB drive "to_upgrade" 12.968
And I plug USB drive "to_upgrade" 3.040
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:16.687
Then the running Tails is installed on USB drive "to_upgrade" 48.358
And I unplug USB drive "to_upgrade" 8.614
And I unplug USB drive "__internal" 3.154
After features/support/hooks.rb:330 4.076
After features/support/hooks.rb:100 0.000
Tags: @product
4:19.139
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.338
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:56.444
Then all tps features from the old Tails version are active 2.087
And Tails is running from USB drive "to_upgrade" 0.581
And the boot device has safe access rights 13.306
And the expected persistent files created with the old Tails version are present in the filesystem 3.324
And all persistent directories from the old Tails version have safe access rights 3.057
After features/support/hooks.rb:330 0.830
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
12:21.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.132
And no SquashFS delta is installed 0.377
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 5.497
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.816
And the file system changes introduced in version 6.2~testoverlayfs are not present 2.392
And the file system changes introduced in version 6.3~testoverlayfs are not present 2.855
When the network is plugged 0.160
And Tor is ready 41.909
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 16.693
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 23.342
Given I shutdown Tails and wait for the computer to power off 19.212
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:38.522
Then Tails is running version 6.2~testoverlayfs 0.035
And all tps features are active 3.098
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.604
When the network is plugged 0.073
And Tor is ready 37.381
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.154
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 32.949
Given I shutdown Tails and wait for the computer to power off 6.384
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:56.542
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 3.141
And the file system changes introduced in version 6.3~testoverlayfs are present 0.787
And only the 6.3~testoverlayfs SquashFS delta is installed 0.108
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.084
And Tor is ready 33.489
Then the Upgrader considers the system as up-to-date 0.318
# 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 22.748
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.183
After features/support/hooks.rb:330 1.010
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
1:30.727
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:30.727
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:330 6.970 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:46:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5730/artifact/build-artifacts/02:46:35_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/5730/artifact/build-artifacts/02:46:35_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5730/artifact/build-artifacts/02:46:35_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5730/artifact/build-artifacts/02:46:35_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000