Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 7 11 Apr 2025, 00:39

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 39:5.672 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:19.595
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 38.028
When I start Tails from USB drive "old" with network unplugged 1:35.885
Then the boot device has safe access rights 3.337
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 7.991
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.698
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:25.944
Then Tails is running from USB drive "old" 0.449
And I create a persistent partition 33.390
And I take note of which tps features are available 1.786
Then a Tails persistence partition exists on USB drive "old" 0.944
And I shutdown Tails and wait for the computer to power off 8.993
After features/support/hooks.rb:330 0.191
After features/support/hooks.rb:100 0.011
Tags: @product
3:4.623
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.548
Then Tails is running from USB drive "old" 1.882
And all tps features are active 3.423
When I write some files expected to persist 3.170
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 3.619
And I take note of which tps features are available 0.552
And I shutdown Tails and wait for the computer to power off 6.842
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.679
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 11.792
And I log in to a new session 19.849
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.636
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.724
Then the running Tails is installed on USB drive "to_upgrade" 22.253
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:330 1.020
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.460
Then all tps features from the old Tails version are active 1.763
And Tails is running from USB drive "to_upgrade" 0.395
And the boot device has safe access rights 3.541
And the expected persistent files created with the old Tails version are present in the filesystem 1.583
And all persistent directories from the old Tails version have safe access rights 2.858
After features/support/hooks.rb:330 1.641
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
25:51.248
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.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.005
And no SquashFS delta is installed 0.190
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.636
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.082
And Tor is ready 21.501
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.169
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.148
Given I shutdown Tails and wait for the computer to power off 8.969
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.276
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.303
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.324
When the network is plugged 0.076
And Tor is ready 19.936
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.627
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.071
Given I shutdown Tails and wait for the computer to power off 4.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:58.921
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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 10.844 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:14:58)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/02:14:58_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/02:14:58_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/02:14:58_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.566
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.445
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.586
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the signing key used by the Upgrader is outdated 0.139
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 20.946
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.258
After features/support/hooks.rb:330 1.045
After features/support/hooks.rb:100 0.000