Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 102 25 Jun 2025, 20:55

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 44 2 41 0 0 87 5 2 7 26:36.722 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
3:52.837
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.083
Given a computer 0.586
And I create a 7200 MiB disk named "old" 0.124
And I plug USB drive "old" 1.468
And I write an old version of the Tails USB image to disk "old" 1:4.816
When I start Tails from USB drive "old" with network unplugged 2:39.575
Then the boot device has safe access rights 4.983
And Tails is running from USB drive "old" 0.396
And there is no persistence partition on USB drive "old" 0.268
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:335 6.124
After features/support/hooks.rb:105 0.117
Tags: @product
4:3.447
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.073
Given a computer 2.715
And I start Tails from USB drive "old" with network unplugged and I login 2:30.129
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 1:10.263
And I take note of which tps features are available 4.827
Then a Tails persistence partition exists on USB drive "old" 0.873
And I shutdown Tails and wait for the computer to power off 14.273
After features/support/hooks.rb:335 1.724
After features/support/hooks.rb:105 0.049
Tags: @product
6:3.005
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.024
Given a computer 0.757
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:26.556
Then Tails is running from USB drive "old" 0.350
And all tps features are active 10.610
When I write some files expected to persist 3.875
# 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.497
And all persistent directories from the old Tails version have safe access rights 4.381
And I take note of which tps features are available 0.619
And I shutdown Tails and wait for the computer to power off 14.279
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 1:0.821
After features/support/hooks.rb:335 0.125
After features/support/hooks.rb:105 0.008
Tags: @product
5:18.620
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 1:8.543
And I log in to a new session 44.071
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.964
And I plug USB drive "to_upgrade" 3.058
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:12.031
Then the running Tails is installed on USB drive "to_upgrade" 1:3.304
And I unplug USB drive "to_upgrade" 0.325
And I unplug USB drive "__internal" 0.321
After features/support/hooks.rb:335 4.116
After features/support/hooks.rb:105 0.000
Tags: @product
4:42.292
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.013
Given a computer 0.703
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:18.633
Then all tps features from the old Tails version are active 2.259
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 14.491
And the expected persistent files created with the old Tails version are present in the filesystem 2.979
And all persistent directories from the old Tails version have safe access rights 2.868
After features/support/hooks.rb:335 5.615
After features/support/hooks.rb:105 0.105
Tags: @product @automatic_upgrade
1:20.633
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.020
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:20.633
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:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
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 file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 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
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.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.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:335 6.937 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:13:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:105 0.000
Tags: @product @automatic_upgrade
1:15.884
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.884
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:335 7.477 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:15:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:15:21_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:15:21_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:15:21_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:15:21_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:105 0.000