Project Number Date
test_Tails_ISO_test-suite-options 11 27 Jun 2025, 21:32

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 28:22.859 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:58.396
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given a computer 0.378
And I create a 7200 MiB disk named "old" 0.111
And I plug USB drive "old" 1.092
And I write an old version of the Tails USB image to disk "old" 42.268
When I start Tails from USB drive "old" with network unplugged 2:2.498
Then the boot device has safe access rights 4.412
And Tails is running from USB drive "old" 0.769
And there is no persistence partition on USB drive "old" 0.541
And process "udev-watchdog" is running 0.568
And udev-watchdog is monitoring the correct device 1.897
And I unplug USB drive "old" 3.858
After features/support/hooks.rb:330 5.062
After features/support/hooks.rb:100 0.010
Tags: @product
3:13.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 2:6.284
Then Tails is running from USB drive "old" 0.418
And I create a persistent partition 52.612
And I take note of which tps features are available 2.368
Then a Tails persistence partition exists on USB drive "old" 0.929
And I shutdown Tails and wait for the computer to power off 10.635
After features/support/hooks.rb:330 0.542
After features/support/hooks.rb:100 0.018
Tags: @product
4:24.936
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:23.887
Then Tails is running from USB drive "old" 0.617
And all tps features are active 1.995
When I write some files expected to persist 1.746
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.368
And all persistence configuration files have safe access rights 0.558
And all persistent directories from the old Tails version have safe access rights 3.186
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 11.210
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.642
After features/support/hooks.rb:330 0.131
After features/support/hooks.rb:100 0.010
Tags: @product
3:16.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.716
And I log in to a new session 27.708
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.932
And I plug USB drive "to_upgrade" 2.619
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.716
Then the running Tails is installed on USB drive "to_upgrade" 37.262
And I unplug USB drive "to_upgrade" 0.267
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:330 3.112
After features/support/hooks.rb:100 0.000
Tags: @product
3:18.696
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:1.640
Then all tps features from the old Tails version are active 1.922
And Tails is running from USB drive "to_upgrade" 0.440
And the boot device has safe access rights 4.171
And the expected persistent files created with the old Tails version are present in the filesystem 5.665
And all persistent directories from the old Tails version have safe access rights 4.656
After features/support/hooks.rb:330 1.008
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
9:47.800
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.016
And no SquashFS delta is installed 0.368
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.014
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.246
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.722
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.573
When the network is plugged 0.073
And Tor is ready 28.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.420
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.150
Given I shutdown Tails and wait for the computer to power off 13.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.561
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 7.643
And the file system changes introduced in version 6.2~testoverlayfs are present 0.793
And only the 6.2~testoverlayfs SquashFS delta is installed 0.118
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.513
# 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.375
When the network is plugged 0.074
And Tor is ready 23.345
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.792
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.562
Given I shutdown Tails and wait for the computer to power off 9.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:9.673
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 3.425
And the file system changes introduced in version 6.3~testoverlayfs are present 1.038
And only the 6.3~testoverlayfs SquashFS delta is installed 0.171
# 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.497
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.460
When the network is plugged 0.094
And Tor is ready 26.400
Then the Upgrader considers the system as up-to-date 0.868
# 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 29.310
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.114
After features/support/hooks.rb:330 3.547
After features/support/hooks.rb:100 0.287
Tags: @product @automatic_upgrade
1:23.094
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.081
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:23.094
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 8.788 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:22:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/11/artifact/build-artifacts/02:22:13_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/11/artifact/build-artifacts/02:22:13_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/11/artifact/build-artifacts/02:22:13_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/11/artifact/build-artifacts/02:22:13_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000