Project Number Date
test_Tails_ISO_20701-migrate-away-from-moox-late 5 19 Dec 2024, 01:47

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 82 1 4 0 0 87 6 1 7 18:47.377 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:4.458
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.113
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 30.422
When I start Tails from USB drive "old" with network unplugged 1:28.731
Then the boot device has safe access rights 2.912
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 7.019
After features/support/hooks.rb:100 0.017
Tags: @product
2:5.694
Before features/support/hooks.rb:269 0.015
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:25.117
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 29.441
And I take note of which tps features are available 1.639
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.223
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.052
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.759
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.003
When I write some files expected to persist 1.894
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.488
And I take note of which tps features are available 0.373
And I shutdown Tails and wait for the computer to power off 4.296
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.134
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.929
Before features/support/hooks.rb:269 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 10.202
And I log in to a new session 20.187
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.702
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.412
Then the running Tails is installed on USB drive "to_upgrade" 22.510
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.062
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.151
Before features/support/hooks.rb:269 0.007
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.533
Then all tps features from the old Tails version are active 1.607
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.432
And the expected persistent files created with the old Tails version are present in the filesystem 1.605
And all persistent directories from the old Tails version have safe access rights 2.392
After features/support/hooks.rb:326 0.667
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
6:50.619
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.533
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.068
And Tor is ready 19.356
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.617
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.382
Given I shutdown Tails and wait for the computer to power off 10.702
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.787
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.117
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.289
# 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.260
When the network is plugged 0.065
And Tor is ready 19.771
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.108
Given I shutdown Tails and wait for the computer to power off 4.392
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.596
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.852
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.063
And Tor is ready 19.584
Then the Upgrader considers the system as up-to-date 10.860
# 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 14.943
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.027
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
10.471
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.031
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.076
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:1395:in `/^the signing key used by the Upgrader is outdated$/'
features/usb_upgrade.feature:130:in `And the signing key used by the Upgrader is outdated'
But a current signing key is available on our website 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:326 5.071 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:47:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/5/artifact/build-artifacts/01:47:50_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/5/artifact/build-artifacts/01:47:50_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/5/artifact/build-artifacts/01:47:50_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/5/artifact/build-artifacts/01:47:50_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000