Project Number Date
test_Tails_ISO_stable 4658 09 Feb 2024, 15:42

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 71 1 15 0 0 87 6 1 7 13:59.061 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:27.340
Before features/support/hooks.rb:245 0.006
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 20.198
When I start Tails from USB drive "old" with network unplugged 1:1.516
Then the boot device has safe access rights 3.354
And Tails is running from USB drive "old" 0.379
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:291 3.590
After features/support/hooks.rb:75 0.008
Tags: @product
2:4.340
Before features/support/hooks.rb:245 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:7.658
Then Tails is running from USB drive "old" 0.446
And I create a persistent partition 44.213
And I take note of which tps features are available 1.698
Then a Tails persistence partition exists on USB drive "old" 0.963
And I shutdown Tails and wait for the computer to power off 9.159
After features/support/hooks.rb:291 0.153
After features/support/hooks.rb:75 0.009
Tags: @product
2:17.870
Before features/support/hooks.rb:245 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:49.787
Then Tails is running from USB drive "old" 0.429
And all tps features are active 2.023
When I write some files expected to persist 1.796
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.834
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 3.081
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.592
After features/support/hooks.rb:291 0.137
After features/support/hooks.rb:75 0.010
Tags: @product
2:39.031
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.573
And I log in to a new session 17.136
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.273
And I plug USB drive "to_upgrade" 2.500
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.074
Then the running Tails is installed on USB drive "to_upgrade" 13.075
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:291 3.145
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.532
Before features/support/hooks.rb:245 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.551
Then all tps features from the old Tails version are active 1.650
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.765
And the expected persistent files created with the old Tails version are present in the filesystem 1.918
And all persistent directories from the old Tails version have safe access rights 3.126
After features/support/hooks.rb:291 0.926
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
3:1.068
Scenario Upgrading an initial Tails installation with an incremental upgrade
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 12.116
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.429
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.158
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.558
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.557
When the network is plugged 0.043
And Tor is ready 17.233
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.918
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.724
Given I shutdown Tails and wait for the computer to power off 6.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.447
Then Tails is running version 2.2~testoverlayfsng 0.158
And all tps features are active 2.659
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.442
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.348
When the network is plugged 0.056
And Tor is ready 15.333
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/proc//status' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:69:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:40:in `loop'
./features/support/helpers/remote_shell.rb:40:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:204:in `open'
./features/support/helpers/remote_shell.rb:222:in `read'
./features/support/helpers/vm_helper.rb:567:in `block in file_content'
./features/support/helpers/vm_helper.rb:566:in `each'
./features/support/helpers/vm_helper.rb:566:in `reduce'
./features/support/helpers/vm_helper.rb:566:in `file_content'
./features/step_definitions/checks.rb:213:in `get_seccomp_status'
./features/step_definitions/checks.rb:238:in `/^Tor is (not )?confined with Seccomp$/'
./features/step_definitions/common_steps.rb:674:in `/^I wait until Tor is ready$/'
./features/step_definitions/common_steps.rb:652:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:603:in `/^Tor is ready$/'
features/usb_upgrade.feature:105:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.000
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 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 2.3~testoverlayfsng 0.000
And all tps features are active 0.000
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.000
And only the 2.3~testoverlayfsng 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 2.1~testoverlayfsng 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 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:291 4.882 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:47:09)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4658/artifact/build-artifacts/01:47:09_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4658/artifact/build-artifacts/01:47:09_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4658/artifact/build-artifacts/01:47:09_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4658/artifact/build-artifacts/01:47:09_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
29.877
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.732
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.322
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the signing key used by the Upgrader is outdated 0.746
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 16.143
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.831
After features/support/hooks.rb:291 0.713
After features/support/hooks.rb:75 0.000