Project Number Date
test_Tails_ISO_5501-plaintext-locale-greeter 11 01 Jun 2025, 09:08

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 57 2 28 0 0 87 5 2 7 14:28.439 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
2:6.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.162
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 32.592
When I start Tails from USB drive "old" with network unplugged 1:28.977
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 6.904
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.203
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:27.150
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 33.408
And I take note of which tps features are available 1.891
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 8.441
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.006
Tags: @product
2:53.569
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.577
Then Tails is running from USB drive "old" 1.399
And all tps features are active 2.264
When I write some files expected to persist 3.026
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.485
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 4.664
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.951
After features/support/hooks.rb:330 0.089
After features/support/hooks.rb:100 0.005
Tags: @product
2:27.265
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.414
And I log in to a new session 13.896
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.238
And I plug USB drive "to_upgrade" 2.522
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.150
Then the running Tails is installed on USB drive "to_upgrade" 25.622
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 3.786
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.672
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.660
Then all tps features from the old Tails version are active 1.525
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.271
And the expected persistent files created with the old Tails version are present in the filesystem 1.322
And all persistent directories from the old Tails version have safe access rights 2.399
After features/support/hooks.rb:330 1.073
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
1:19.057
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.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.651
And no SquashFS delta is installed 0.716
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.072
And Tor is ready 1:2.246
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:652:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:89:in `And Tor is ready'
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 9.512 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:32:00)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:32:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:32:00_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_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:32:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:32:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:32:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
1:12.731
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.962
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 1:2.212
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:652:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:133:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:330 8.735 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:33:23)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:33:23_Upgrading_a_Tails_whose_signing_key_is_outdated_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:33:23_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:33:23_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:33:23_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/11/artifact/build-artifacts/01:33:23_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000