Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 13 17 Oct 2026, 05:58

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 9:50.013 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:4.347
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.773
When I start Tails from USB drive "old" with network unplugged 47.179
Then the boot device has safe access rights 1.780
And Tails is running from USB drive "old" 0.166
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.136
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.716
After features/support/hooks.rb:108 0.032
Tags: @product
1:20.814
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 47.857
Then Tails is running from USB drive "old" 0.221
And I create a persistent partition 23.431
And I take note of which tps features are available 6.139
Then a Tails persistence partition exists on USB drive "old" 0.488
And I shutdown Tails and wait for the computer to power off 2.579
After features/support/hooks.rb:339 0.518
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.978
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.945
Then Tails is running from USB drive "old" 0.251
And all tps features are active 7.314
When I write some files expected to persist 1.212
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 1.491
And I take note of which tps features are available 5.963
And I shutdown Tails and wait for the computer to power off 2.596
# 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.578
After features/support/hooks.rb:339 0.359
After features/support/hooks.rb:108 0.006
Tags: @product
51.987
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.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 8.102
And I log in to a new session 10.917
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.616
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 30.082
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
STDOUT:

STDERR:
Exception ignored in: <function Ponytail.__del__ at 0x7d23d8101440>
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/ponytail/ponytail.py", line 51, in __del__
    if (self.connected):
AttributeError: 'Ponytail' object has no attribute 'connected'


./features/support/helpers/dogtail.rb:85:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1107:in `new'
./features/step_definitions/common_steps.rb:1107:in `block in launch_app'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:1106:in `launch_app'
./features/step_definitions/common_steps.rb:1140:in `launch_console'
./features/step_definitions/common_steps.rb:1002:in `block in <top (required)>'
./features/step_definitions/usb.rb:155:in `block in <top (required)>'
./features/step_definitions/usb.rb:195:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1106:in `launch_app'
./features/step_definitions/common_steps.rb:1140:in `launch_console'
./features/step_definitions/common_steps.rb:1002:in `/^I run "([^"]+)" in Console$/'
./features/step_definitions/usb.rb:155:in `/^I start Tails Installer$/'
./features/step_definitions/usb.rb:195: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:339 10.574 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:13:44)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21736-reject-unsupported-installs/13/artifact/build-artifacts/01:13:44_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21736-reject-unsupported-installs/13/artifact/build-artifacts/01:13:44_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21736-reject-unsupported-installs/13/artifact/build-artifacts/01:13:44_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.063
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.470
Then all tps features from the old Tails version are active 1.032
And Tails is running from USB drive "to_upgrade" 0.200
And the boot device has safe access rights 1.998
And the expected persistent files created with the old Tails version are present in the filesystem 0.788
And all persistent directories from the old Tails version have safe access rights 1.498
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.031
Tags: @product @automatic_upgrade
3:34.306
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 20.894
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.181
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.279
When the network is plugged 0.031
And Tor is ready 11.614
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.921
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.247
Given I shutdown Tails and wait for the computer to power off 5.214
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.922
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.461
And the file system changes introduced in version 6.2~testoverlayfs are present 0.157
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.168
When the network is plugged 0.043
And Tor is ready 10.522
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.885
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.404
Given I shutdown Tails and wait for the computer to power off 5.031
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.171
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.605
And the file system changes introduced in version 6.3~testoverlayfs are present 0.259
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.082
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.145
When the network is plugged 0.030
And Tor is ready 9.978
Then the Upgrader considers the system as up-to-date 0.120
# 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 3.024
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.377
After features/support/hooks.rb:339 0.979
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.515
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 7.827
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.178
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.029
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 7.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.432
After features/support/hooks.rb:339 0.615
After features/support/hooks.rb:108 0.000