Project Number Date
test_Tails_ISO_devel 3239 16 Jan 2024, 19: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 17:38.795 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:33.764
Before features/support/hooks.rb:245 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 20.440
When I start Tails from USB drive "old" with network unplugged 1:7.741
Then the boot device has safe access rights 3.232
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:291 3.500
After features/support/hooks.rb:75 0.010
Tags: @product
1:57.766
Before features/support/hooks.rb:245 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:4.427
Then Tails is running from USB drive "old" 0.533
And I create a persistent partition 43.183
And I take note of which tps features are available 1.423
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 7.083
After features/support/hooks.rb:291 0.112
After features/support/hooks.rb:75 0.009
Tags: @product
2:23.480
Before features/support/hooks.rb:245 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:56.749
Then Tails is running from USB drive "old" 0.413
And all tps features are active 2.361
When I write some files expected to persist 1.913
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.280
And all persistence configuration files have safe access rights 0.623
And all persistent directories from the old Tails version have safe access rights 2.635
And I take note of which tps features are available 0.566
And I shutdown Tails and wait for the computer to power off 3.072
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.660
After features/support/hooks.rb:291 0.124
After features/support/hooks.rb:75 0.009
Tags: @product
2:33.628
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.128
And I log in to a new session 16.108
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.138
And I plug USB drive "to_upgrade" 2.549
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.342
Then the running Tails is installed on USB drive "to_upgrade" 12.942
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:291 6.671
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.079
Before features/support/hooks.rb:245 0.007
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.203
Then all tps features from the old Tails version are active 1.907
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.744
And the expected persistent files created with the old Tails version are present in the filesystem 1.707
And all persistent directories from the old Tails version have safe access rights 2.940
After features/support/hooks.rb:291 0.699
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:49.850
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.281
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.392
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.052
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.446
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.530
When the network is plugged 0.033
And Tor is ready 16.013
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.861
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.601
Given I shutdown Tails and wait for the computer to power off 9.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.984
Then Tails is running version 2.2~testoverlayfsng 0.101
And all tps features are active 2.320
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.485
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.335
When the network is plugged 0.038
And Tor is ready 14.604
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.693
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.199
Given I shutdown Tails and wait for the computer to power off 4.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.408
Then Tails is running version 2.3~testoverlayfsng 0.128
And all tps features are active 2.197
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.639
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.065
# 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.287
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.338
When the network is plugged 0.046
And Tor is ready 16.360
Then the Upgrader considers the system as up-to-date 0.294
# 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.224
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.609
After features/support/hooks.rb:291 0.745
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
1:21.225
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 9.972
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.319
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.067
And the signing key used by the Upgrader is outdated 1.161
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 1:9.655
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.313 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:55:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3239/artifact/build-artifacts/01:55:17_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3239/artifact/build-artifacts/01:55:17_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3239/artifact/build-artifacts/01:55:17_Upgrading_a_Tails_whose_signing_key_is_outdated.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3239/artifact/build-artifacts/01:55:17_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:75 0.000