Project Number Date
test_Tails_ISO_stable 4544 30 Nov 2023, 21:25

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 85 1 1 0 0 87 6 1 7 18:19.511 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:38.814
Before features/support/hooks.rb:245 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.093
And I write an old version of the Tails USB image to disk "old" 20.063
When I start Tails from USB drive "old" with network unplugged 1:13.294
Then the boot device has safe access rights 3.167
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:291 3.722
After features/support/hooks.rb:75 0.009
Tags: @product
2:1.531
Before features/support/hooks.rb:245 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:6.046
Then Tails is running from USB drive "old" 0.430
And I create a persistent partition 43.978
And I take note of which tps features are available 1.652
Then a Tails persistence partition exists on USB drive "old" 0.988
And I shutdown Tails and wait for the computer to power off 8.250
After features/support/hooks.rb:291 0.235
After features/support/hooks.rb:75 0.018
Tags: @product
2:30.439
Before features/support/hooks.rb:245 0.009
Given a computer 0.301
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:57.058
Then Tails is running from USB drive "old" 0.425
And all tps features are active 4.391
When I write some files expected to persist 1.948
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.623
And all persistent directories from the old Tails version have safe access rights 3.108
And I take note of which tps features are available 2.340
And I shutdown Tails and wait for the computer to power off 3.161
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.834
After features/support/hooks.rb:291 0.139
After features/support/hooks.rb:75 0.008
Tags: @product
2:37.238
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.977
And I log in to a new session 16.129
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.292
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.137
Then the running Tails is installed on USB drive "to_upgrade" 13.900
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.172
After features/support/hooks.rb:291 0.936
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.335
Before features/support/hooks.rb:245 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.003
Then all tps features from the old Tails version are active 2.165
And Tails is running from USB drive "to_upgrade" 0.399
And the boot device has safe access rights 3.827
And the expected persistent files created with the old Tails version are present in the filesystem 1.913
And all persistent directories from the old Tails version have safe access rights 2.832
After features/support/hooks.rb:291 0.749
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:7.127
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.950
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.421
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.075
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.473
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.610
When the network is plugged 0.040
And Tor is ready 17.573
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.683
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.877
Given I shutdown Tails and wait for the computer to power off 7.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.383
Then Tails is running version 2.2~testoverlayfsng 0.122
And all tps features are active 2.699
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.464
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.371
When the network is plugged 0.055
And Tor is ready 15.903
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.869
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.159
Given I shutdown Tails and wait for the computer to power off 4.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.429
Then Tails is running version 2.3~testoverlayfsng 0.107
And all tps features are active 2.522
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.712
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.090
# 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.324
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.529
When the network is plugged 0.038
And Tor is ready 15.217
Then the Upgrader considers the system as up-to-date 0.370
# 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 29.510
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.118
After features/support/hooks.rb:291 0.792
After features/support/hooks.rb:75 0.026
Tags: @product @automatic_upgrade
1:23.025
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:245 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.644
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.361
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the signing key used by the Upgrader is outdated 0.600
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 1:11.304
The 
The system is not fully running yet:
No jobs running.

  UNIT               LOAD   ACTIVE SUB    DESCRIPTION
● session-c194.scope loaded failed failed Session c194 of user root

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
 (RuntimeError)
./features/step_definitions/common_steps.rb:642:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:637:in `/^I wait until Tor is ready$/'
./features/step_definitions/common_steps.rb:605:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:556: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 2.2~testoverlayfsng 0.000
After features/support/hooks.rb:291 4.356 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:53:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/01:53:59_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/01:53:59_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/01:53:59_Upgrading_a_Tails_whose_signing_key_is_outdated.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/01:53:59_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:75 0.000