Project Number Date
test_Tails_ISO_21079-secure-boot-disabled 4 02 May 2026, 13:23

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 83 1 3 0 0 87 6 1 7 11:41.234 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:20.857
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.001
When I start Tails from USB drive "old" with network unplugged 1:2.062
Then the boot device has safe access rights 2.971
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:331 3.793
After features/support/hooks.rb:100 0.047
Tags: @product
1:31.313
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 56.720
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 25.716
And I take note of which tps features are available 0.839
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 6.923
After features/support/hooks.rb:331 0.612
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.021
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.149
Then Tails is running from USB drive "old" 0.286
And all tps features are active 1.143
When I write some files expected to persist 1.397
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.494
And all persistent directories from the old Tails version have safe access rights 2.105
And I take note of which tps features are available 0.299
And I shutdown Tails and wait for the computer to power off 8.265
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.604
After features/support/hooks.rb:331 0.510
After features/support/hooks.rb:100 0.008
Tags: @product
43.455
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.004
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.789
And I log in to a new session 12.960
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.114
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 18.212
cannot 
cannot find TailsClonerWindow.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/usb.rb:156:in `/^I start Tails Installer$/'
./features/step_definitions/usb.rb:187:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_upgrade.feature:65:in `When I upgrade Tails to USB drive "to_upgrade" by cloning'
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 5.373 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:01:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21079-secure-boot-disabled/4/artifact/build-artifacts/01:01:26_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_21079-secure-boot-disabled/4/artifact/build-artifacts/01:01:26_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21079-secure-boot-disabled/4/artifact/build-artifacts/01:01:26_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21079-secure-boot-disabled/4/artifact/build-artifacts/01:01:26_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.003
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.951
Then all tps features from the old Tails version are active 1.262
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.779
And the expected persistent files created with the old Tails version are present in the filesystem 1.479
And all persistent directories from the old Tails version have safe access rights 2.214
After features/support/hooks.rb:331 0.839
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:52.684
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 with a persistent partition enabled and logged in 8.696
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.417
When the network is plugged 0.022
And Tor is ready 22.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.429
Given I shutdown Tails and wait for the computer to power off 20.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.905
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.313
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
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.142
# 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.230
When the network is plugged 0.019
And Tor is ready 21.158
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.401
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.678
Given I shutdown Tails and wait for the computer to power off 17.681
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.292
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.192
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.183
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.019
And Tor is ready 22.732
Then the Upgrader considers the system as up-to-date 0.117
# 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.342
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.510
After features/support/hooks.rb:331 0.944
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
27.898
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 8.008
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 18.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.531
After features/support/hooks.rb:331 1.166
After features/support/hooks.rb:100 0.000