Project Number Date
test_Tails_ISO_feature-arti 92 17 Jun 2025, 16:44

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 55 2 30 0 0 87 5 2 7 20:49.556 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
3:19.599
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 3.054
And I create a 7200 MiB disk named "old" 0.453
And I plug USB drive "old" 1.467
And I write an old version of the Tails USB image to disk "old" 59.758
When I start Tails from USB drive "old" with network unplugged 2:9.294
Then the boot device has safe access rights 4.444
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:330 10.107
After features/support/hooks.rb:100 0.019
Tags: @product
3:15.834
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.378
And I start Tails from USB drive "old" with network unplugged and I login 2:8.812
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 50.173
And I take note of which tps features are available 3.256
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 12.063
After features/support/hooks.rb:330 0.970
After features/support/hooks.rb:100 0.025
Tags: @product
4:41.431
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.341
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:34.632
Then Tails is running from USB drive "old" 2.224
And all tps features are active 4.543
When I write some files expected to persist 2.739
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.511
And I take note of which tps features are available 0.606
And I shutdown Tails and wait for the computer to power off 6.198
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 46.946
After features/support/hooks.rb:330 0.418
After features/support/hooks.rb:100 0.047
Tags: @product
4:10.805
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.308
And I log in to a new session 35.952
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.762
And I plug USB drive "to_upgrade" 5.819
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:15.429
Then the running Tails is installed on USB drive "to_upgrade" 53.995
And I unplug USB drive "to_upgrade" 0.294
And I unplug USB drive "__internal" 0.244
After features/support/hooks.rb:330 5.826
After features/support/hooks.rb:100 0.000
Tags: @product
3:33.691
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.088
Given a computer 1.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:13.219
Then all tps features from the old Tails version are active 8.086
And Tails is running from USB drive "to_upgrade" 0.703
And the boot device has safe access rights 4.734
And the expected persistent files created with the old Tails version are present in the filesystem 1.875
And all persistent directories from the old Tails version have safe access rights 4.022
After features/support/hooks.rb:330 4.406
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
1:4.927
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.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 39.349
And no SquashFS delta is installed 0.576
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.246
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.001
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.801
When the network is plugged 21.556
Command 
Command failed (pid 20971 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/usb_upgrade.feature:88:in `When the network is plugged'
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:330 3:37.987 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:26:49)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_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_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:26:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
43.267
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.391
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.991
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.651
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the signing key used by the Upgrader is outdated 0.142
But a current signing key is available on our website 0.000
When the network is plugged 22.355
Command 
Command failed (pid 21134 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-arti/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:170:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:164:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:186:in `/^the network is plugged$/'
features/usb_upgrade.feature:132:in `When the network is plugged'
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:330 6.862 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:31:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/92/artifact/build-artifacts/02:31:11_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000