Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 8 05 May 2026, 00:37

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 31 4 52 0 0 87 3 4 7 13:28.532 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:1.837
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.006
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.183
When I start Tails from USB drive "old" with network unplugged 44.224
Then the boot device has safe access rights 2.699
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 1.276
After features/support/hooks.rb:100 0.008
Tags: @product
1:25.555
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 52.028
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 24.099
And I take note of which tps features are available 0.651
Then a Tails persistence partition exists on USB drive "old" 0.524
And I shutdown Tails and wait for the computer to power off 7.982
After features/support/hooks.rb:331 0.302
After features/support/hooks.rb:100 0.005
Tags: @product
1:23.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.446
Then Tails is running from USB drive "old" 0.235
And all tps features are active 1.123
When I write some files expected to persist 1.278
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 1.901
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 7.766
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.858
After features/support/hooks.rb:331 0.461
After features/support/hooks.rb:100 0.005
Tags: @product
3:12.747
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.001
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.429
And I log in to a new session 3:5.317
cannot 
cannot find GnomeApplicationsMenu.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/common_steps.rb:601:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:542:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/usb_upgrade.feature:62:in `And I log in to a new session'
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.000
And I plug USB drive "to_upgrade" 0.000
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 5.067 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:08:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:08:46_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_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:08:46_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:08:46_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:08:46_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
0.059
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Steps
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 0.010
Call 
Call to virStorageVolLookupByName failed: Storage volume not found: no storage vol with matching name 'to_upgrade' (Libvirt::RetrieveError)
./features/support/helpers/storage_helper.rb:151:in `lookup_volume_by_name'
./features/support/helpers/storage_helper.rb:151:in `disk_path'
./features/support/helpers/vm_helper.rb:337:in `plug_drive'
./features/support/helpers/vm_helper.rb:416:in `set_disk_boot'
./features/step_definitions/common_steps.rb:108:in `/^the computer is set to boot from (.+?) drive "(.+?)"$/'
./features/step_definitions/common_steps.rb:233:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
Hooks
After features/support/hooks.rb:331 4.392
Error message 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/hooks.rb:465:in `block (2 levels) in <top (required)>'
./features/support/hooks.rb:460:in `each'
./features/support/hooks.rb:460:in `After'
Output 1 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:08:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:08:51_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:08:51_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
3:12.407
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 3:12.407
cannot 
cannot find GnomeApplicationsMenu.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/common_steps.rb:601:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:542:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137: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:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
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 file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 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
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.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.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:331 5.439 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:12:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:12:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:12:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:12:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:12:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
3:12.536
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 3:12.536
cannot 
cannot find GnomeApplicationsMenu.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/common_steps.rb:601:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:542:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137: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:331 5.408 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:15:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:15:26_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:15:26_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:15:26_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry/8/artifact/build-artifacts/01:15:26_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000