Project Number Date
test_Tails_ISO_stable 5996 10 Dec 2025, 07:37

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 82 1 4 0 0 87 6 1 7 13:9.331 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:45.286
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.075
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 26.994
When I start Tails from USB drive "old" with network unplugged 1:12.213
Then the boot device has safe access rights 3.780
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:331 4.003
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:24.884
Then Tails is running from USB drive "old" 0.404
And I create a persistent partition 29.256
And I take note of which tps features are available 1.235
Then a Tails persistence partition exists on USB drive "old" 0.715
And I shutdown Tails and wait for the computer to power off 7.798
After features/support/hooks.rb:331 0.542
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.282
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.014
Then Tails is running from USB drive "old" 0.299
And all tps features are active 1.999
When I write some files expected to persist 1.888
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.546
And I take note of which tps features are available 0.591
And I shutdown Tails and wait for the computer to power off 7.594
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.078
After features/support/hooks.rb:331 0.575
After features/support/hooks.rb:100 0.009
Tags: @product
34.563
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.802
And I log in to a new session 10.309
And I clone USB drive "old" to a new USB drive "to_upgrade" 12.945
And I plug USB drive "to_upgrade" 1.505
Call 
Call to virDomainAttachDeviceFlags failed: internal error: cannot update AppArmor profile 'libvirt-203552d5-819c-41f3-800e-2c8ef2545404' (Guestfs::Error)
./features/support/helpers/vm_helper.rb:306:in `attach_device'
./features/support/helpers/vm_helper.rb:306:in `plug_device'
./features/support/helpers/vm_helper.rb:345:in `plug_drive'
./features/step_definitions/common_steps.rb:124:in `/^I plug (.+) drive "([^"]+)"$/'
features/usb_upgrade.feature:64:in `And I plug USB drive "to_upgrade"'
When I upgrade Tails to USB drive "to_upgrade" by cloning 0.000
Then the running Tails is installed on USB drive "to_upgrade" 0.000
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:331 6.248 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:22:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5996/artifact/build-artifacts/01:22:39_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/5996/artifact/build-artifacts/01:22:39_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5996/artifact/build-artifacts/01:22:39_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5996/artifact/build-artifacts/01:22:39_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
1:53.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 5.385
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.770
Then all tps features from the old Tails version are active 1.541
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 3.573
And the expected persistent files created with the old Tails version are present in the filesystem 1.515
And all persistent directories from the old Tails version have safe access rights 2.681
After features/support/hooks.rb:331 0.647
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
4:18.102
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.887
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.531
When the network is plugged 0.309
And Tor is ready 13.264
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.757
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.696
Given I shutdown Tails and wait for the computer to power off 8.134
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.382
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.570
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.184
# 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.239
When the network is plugged 0.162
And Tor is ready 11.807
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.993
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.846
Given I shutdown Tails and wait for the computer to power off 7.618
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.309
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.666
And the file system changes introduced in version 6.3~testoverlayfs are present 0.508
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.234
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.085
And Tor is ready 12.082
Then the Upgrader considers the system as up-to-date 0.172
# 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 7.632
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.654
After features/support/hooks.rb:331 1.313
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
23.215
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.238
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 10.555
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.940
After features/support/hooks.rb:331 0.755
After features/support/hooks.rb:100 0.000