Project Number Date
test_Tails_ISO_improve-cmd-logging 3 17 Jul 2025, 16:58

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 46:54.796 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:38.196
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.342
And I create a 7200 MiB disk named "old" 0.159
And I plug USB drive "old" 1.163
And I write an old version of the Tails USB image to disk "old" 1:0.012
When I start Tails from USB drive "old" with network unplugged 2:29.011
Then the boot device has safe access rights 6.295
And Tails is running from USB drive "old" 0.433
And there is no persistence partition on USB drive "old" 0.097
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 5.718
After features/support/hooks.rb:100 0.043
Tags: @product
4:11.362
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 1.307
And I start Tails from USB drive "old" with network unplugged and I login 2:40.972
Then Tails is running from USB drive "old" 6.726
And I create a persistent partition 1:1.960
And I take note of which tps features are available 2.473
Then a Tails persistence partition exists on USB drive "old" 1.216
And I shutdown Tails and wait for the computer to power off 16.706
After features/support/hooks.rb:330 0.115
After features/support/hooks.rb:100 0.007
Tags: @product
5:20.206
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:57.890
Then Tails is running from USB drive "old" 1.767
And all tps features are active 2.251
When I write some files expected to persist 3.248
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.759
And all persistent directories from the old Tails version have safe access rights 12.484
And I take note of which tps features are available 0.537
And I shutdown Tails and wait for the computer to power off 5.149
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 55.661
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.006
Tags: @product
4:38.066
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 29.282
And I log in to a new session 40.946
And I clone USB drive "old" to a new USB drive "to_upgrade" 9.075
And I plug USB drive "to_upgrade" 3.327
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:21.030
Then the running Tails is installed on USB drive "to_upgrade" 52.558
And I unplug USB drive "to_upgrade" 1.076
And I unplug USB drive "__internal" 0.768
After features/support/hooks.rb:330 4.095
After features/support/hooks.rb:100 0.000
Tags: @product
4:2.580
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.239
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:39.511
Then all tps features from the old Tails version are active 2.877
And Tails is running from USB drive "to_upgrade" 0.405
And the boot device has safe access rights 14.129
And the expected persistent files created with the old Tails version are present in the filesystem 1.888
And all persistent directories from the old Tails version have safe access rights 3.528
After features/support/hooks.rb:330 0.775
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
23:41.701
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 with a persistent partition enabled and logged in 9:38.321
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.596
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.178
And Tor is ready 35.678
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 17.222
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 26.467
Given I shutdown Tails and wait for the computer to power off 2:40.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:52.623
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.447
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.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.416
# 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.444
When the network is plugged 0.093
And Tor is ready 37.143
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.937
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 21.000
Given I shutdown Tails and wait for the computer to power off 11.613
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:43.229
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.530
And the file system changes introduced in version 6.3~testoverlayfs are present 0.988
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.074
And Tor is ready 33.954
Then the Upgrader considers the system as up-to-date 0.416
# 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 25.744
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.045
After features/support/hooks.rb:330 7.242
After features/support/hooks.rb:100 0.081
Tags: @product @automatic_upgrade
1:22.682
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:22.682
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 7.171 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:01:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:01:39_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:01:39_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:01:39_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/03:01:39_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000