Project Number Date
test_Tails_ISO_21734-bump-snapshot-restore-timeout 3 18 Aug 2026, 15:52

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 11:34.639 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
1:15.695
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.111
And I create a 7200 MiB disk named "old" 0.154
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.523
When I start Tails from USB drive "old" with network unplugged 57.971
Then the boot device has safe access rights 2.354
And Tails is running from USB drive "old" 0.167
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.148
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.381
After features/support/hooks.rb:108 0.067
Tags: @product
1:26.777
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 51.195
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 23.748
And I take note of which tps features are available 6.617
Then a Tails persistence partition exists on USB drive "old" 0.606
And I shutdown Tails and wait for the computer to power off 4.257
After features/support/hooks.rb:339 0.529
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.183
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.079
Then Tails is running from USB drive "old" 0.225
And all tps features are active 7.310
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 1.489
And I take note of which tps features are available 7.168
And I shutdown Tails and wait for the computer to power off 4.102
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.942
After features/support/hooks.rb:339 0.196
After features/support/hooks.rb:108 0.012
Tags: @product
2:12.218
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 5.397
And I log in to a new session 12.290
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.852
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.743
Then the running Tails is installed on USB drive "to_upgrade" 19.420
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:339 3.443
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.746
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.299
Then all tps features from the old Tails version are active 1.206
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 2.583
And the expected persistent files created with the old Tails version are present in the filesystem 1.476
And all persistent directories from the old Tails version have safe access rights 1.888
After features/support/hooks.rb:339 0.900
After features/support/hooks.rb:108 0.076
Tags: @product @automatic_upgrade
3:33.167
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 4.641
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.035
And Tor is ready 13.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.969
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.354
Given I shutdown Tails and wait for the computer to power off 5.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.218
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.920
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.234
When the network is plugged 0.035
And Tor is ready 10.383
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.975
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.777
Given I shutdown Tails and wait for the computer to power off 4.031
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.580
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.466
And the file system changes introduced in version 6.3~testoverlayfs are present 0.330
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.035
And Tor is ready 10.523
Then the Upgrader considers the system as up-to-date 0.118
# 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 4.434
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.638
After features/support/hooks.rb:339 0.684
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
17.851
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 4.623
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 12.879
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:553:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:706:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:660: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:339 5.112 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:20:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:20:59_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:20:59_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:20:59_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:20:59_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:108 0.000