Project Number Date
test_Tails_ISO_stable 6564 06 Aug 2026, 12:59

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 84 1 2 0 0 87 6 1 7 11:20.010 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:10.553
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.919
When I start Tails from USB drive "old" with network unplugged 52.480
Then the boot device has safe access rights 2.307
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.537
After features/support/hooks.rb:108 0.007
Tags: @product
1:25.681
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 49.557
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 24.425
And I take note of which tps features are available 6.759
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 4.103
After features/support/hooks.rb:339 0.192
After features/support/hooks.rb:108 0.012
Tags: @product
1:40.047
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.574
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.967
Then Tails is running from USB drive "old" 0.375
And all tps features are active 8.503
When I write some files expected to persist 1.302
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 1.798
And I take note of which tps features are available 6.781
And I shutdown Tails and wait for the computer to power off 4.222
# 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" 12.019
After features/support/hooks.rb:339 0.391
After features/support/hooks.rb:108 0.006
Tags: @product
1:54.747
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.423
And I log in to a new session 11.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.793
And I plug USB drive "to_upgrade" 2.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.294
Then the running Tails is installed on USB drive "to_upgrade" 0.839
Command 
Command failed: udisksctl info --block-device '/dev/sdb1'
error code: 1
stdout: 
stderr: Error looking up object for device /dev/sdb1
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/usb.rb:548:in `check_part_integrity'
./features/step_definitions/usb.rb:572:in `tails_is_installed_helper'
./features/step_definitions/usb.rb:610:in `/^the running Tails is installed on USB drive "([^"]+)"$/'
features/usb_upgrade.feature:66:in `Then the running Tails is installed on USB drive "to_upgrade"'
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:339 5.393 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:17:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/01:17:03_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/01:17:03_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/01:17:03_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/01:17:03_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.193
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.478
Then all tps features from the old Tails version are active 1.101
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.530
And the expected persistent files created with the old Tails version are present in the filesystem 1.007
And all persistent directories from the old Tails version have safe access rights 1.782
After features/support/hooks.rb:339 0.485
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:36.152
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 8.403
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.031
And Tor is ready 14.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.910
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.922
Given I shutdown Tails and wait for the computer to power off 5.755
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.950
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.407
And the file system changes introduced in version 6.2~testoverlayfs are present 0.190
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.108
# 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.192
When the network is plugged 0.025
And Tor is ready 10.787
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.900
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.533
Given I shutdown Tails and wait for the computer to power off 2.552
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.332
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 8.588
And the file system changes introduced in version 6.3~testoverlayfs are present 0.439
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.030
And Tor is ready 10.765
Then the Upgrader considers the system as up-to-date 0.164
# 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.264
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.470
After features/support/hooks.rb:339 0.691
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
20.635
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.095
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 10.302
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.833
After features/support/hooks.rb:339 0.546
After features/support/hooks.rb:108 0.000