Project Number Date
test_Tails_ISO_devel 3226 08 Jan 2024, 17:30

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:2.254 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.689
Before features/support/hooks.rb:245 0.008
Given a computer 0.252
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 19.323
When I start Tails from USB drive "old" with network unplugged 1:5.421
Then the boot device has safe access rights 3.504
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:291 3.597
After features/support/hooks.rb:75 0.085
Tags: @product
2:0.100
Before features/support/hooks.rb:245 0.008
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:7.184
Then Tails is running from USB drive "old" 0.424
And I create a persistent partition 43.017
And I take note of which tps features are available 1.299
Then a Tails persistence partition exists on USB drive "old" 0.880
And I shutdown Tails and wait for the computer to power off 7.101
After features/support/hooks.rb:291 0.171
After features/support/hooks.rb:75 0.011
Tags: @product
2:26.079
Before features/support/hooks.rb:245 0.006
Given a computer 0.297
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:56.001
Then Tails is running from USB drive "old" 0.392
And all tps features are active 2.388
When I write some files expected to persist 2.101
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.643
And all persistent directories from the old Tails version have safe access rights 4.092
And I take note of which tps features are available 0.544
And I shutdown Tails and wait for the computer to power off 3.053
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.344
After features/support/hooks.rb:291 0.140
After features/support/hooks.rb:75 0.010
Tags: @product
2:34.930
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.466
And I log in to a new session 15.863
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.253
And I plug USB drive "to_upgrade" 2.474
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.753
Then the running Tails is installed on USB drive "to_upgrade" 14.745
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 0.815
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.233
Before features/support/hooks.rb:245 0.008
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.046
Then all tps features from the old Tails version are active 1.754
And Tails is running from USB drive "to_upgrade" 0.419
And the boot device has safe access rights 3.979
And the expected persistent files created with the old Tails version are present in the filesystem 1.816
And all persistent directories from the old Tails version have safe access rights 3.016
After features/support/hooks.rb:291 0.685
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:3.289
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.853
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.298
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.067
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.644
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.478
When the network is plugged 0.034
And Tor is ready 19.484
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.137
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.953
Given I shutdown Tails and wait for the computer to power off 5.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.687
Then Tails is running version 2.2~testoverlayfsng 0.118
And all tps features are active 2.326
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.448
And only the 2.2~testoverlayfsng 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.319
# 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.339
When the network is plugged 0.034
And Tor is ready 14.328
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.898
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.142
Given I shutdown Tails and wait for the computer to power off 4.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.020
Then Tails is running version 2.3~testoverlayfsng 0.111
And all tps features are active 2.049
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.661
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.074
# 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.311
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.334
When the network is plugged 0.044
And Tor is ready 17.049
Then the Upgrader considers the system as up-to-date 0.307
# 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 26.047
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.570
After features/support/hooks.rb:291 0.868
After features/support/hooks.rb:75 0.047
Tags: @product @automatic_upgrade
1:22.931
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:245 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.951
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.397
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the signing key used by the Upgrader is outdated 1.905
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 1:10.555
The 
The system is not fully running yet:
No jobs running.

  UNIT               LOAD   ACTIVE SUB    DESCRIPTION
● session-c195.scope loaded failed failed Session c195 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.430 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:56:36)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3226/artifact/build-artifacts/01:56:36_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3226/artifact/build-artifacts/01:56:36_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3226/artifact/build-artifacts/01:56:36_Upgrading_a_Tails_whose_signing_key_is_outdated.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3226/artifact/build-artifacts/01:56:36_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:75 0.000