Project Number Date
test_Tails_ISO_20701-migrate-away-from-moox-late 8 19 Dec 2024, 09:33

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 42 1 0 0 0 43 1 1 2 15:54.909 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 @automatic_upgrade
13:36.282
Before features/support/hooks.rb:269 0.037
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7:9.466
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.649
And Tor is ready 19.066
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.424
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.280
Given I shutdown Tails and wait for the computer to power off 4.847
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.872
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.716
And the file system changes introduced in version 6.2~testoverlayfs are present 0.391
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.302
When the network is plugged 0.113
And Tor is ready 21.366
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.630
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.002
Given I shutdown Tails and wait for the computer to power off 6.490
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.045
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.057
And the file system changes introduced in version 6.3~testoverlayfs are present 0.451
And only the 6.3~testoverlayfs 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.069
And Tor is ready 17.086
Then the Upgrader considers the system as up-to-date 0.315
# 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 16.292
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.028
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
2:18.626
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:269 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 20.393
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1:48.500
Tor 
Tor operation failed (despite retrying 10 times) with
Test::Unit::AssertionFailedError: <"TailsUpgraderUpgradeTo6.2~testoverlayfs.png"> expected but was
<"TailsUpgraderFailure.png">. (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1298:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:326 5.031 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 00:16:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/8/artifact/build-artifacts/00:16:16_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/8/artifact/build-artifacts/00:16:16_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/8/artifact/build-artifacts/00:16:16_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/8/artifact/build-artifacts/00:16:16_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000