Project Number Date
test_Tails_ISO_feature-arti 22 08 Apr 2025, 16:30

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 58 4 25 0 0 87 3 4 7 13:37.106 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:30.189
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 27.568
When I start Tails from USB drive "old" with network unplugged 1:1.347
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295: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:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 4.828

SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:25:49)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:25:49_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:25:49_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:25:49_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:25:49_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal

After features/support/hooks.rb:100 0.008
Tags: @product
36.722
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 36.543
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295: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:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 4.798

SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:26:30)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:26:30_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:26:30_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:26:30_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:26:30_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.008
Tags: @product
37.110
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 36.928
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295: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:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 4.788

SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:27:12)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:27:12_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:27:12_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:27:12_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:27:12_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.010
Tags: @product
2:32.445
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.619
And I log in to a new session 19.556
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.259
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.004
Then the running Tails is installed on USB drive "to_upgrade" 24.119
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:330 1.865
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.877
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.006
Steps
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.695
The
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:302: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
After features/support/hooks.rb:330 5.046

SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:31:11)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:31:11_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:31:11_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:31:11_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/22/artifact/build-artifacts/02:31:11_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:100 0.008
6:24.612
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 11.648
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.080
And Tor is ready 19.407
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.395
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.179
Given I shutdown Tails and wait for the computer to power off 8.502
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.413
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.976
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.317
When the network is plugged 0.076
And Tor is ready 18.055
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.321
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.703
Given I shutdown Tails and wait for the computer to power off 4.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.938
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.995
And the file system changes introduced in version 6.3~testoverlayfs are present 0.568
And only the 6.3~testoverlayfs SquashFS delta is installed 0.119
# 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.415
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.085
And Tor is ready 20.284
Then the Upgrader considers the system as up-to-date 0.282
# 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 14.662
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.420
After features/support/hooks.rb:330 0.772
After features/support/hooks.rb:100 0.016
36.148
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 9.806
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.577
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the signing key used by the Upgrader is outdated 0.112
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 17.639
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.792
After features/support/hooks.rb:330 0.904
After features/support/hooks.rb:100 0.000