Project Number Date
test_Tails_ISO_20701-migrate-away-from-moox-late 2 18 Dec 2024, 16:44

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 55 2 30 0 0 87 5 2 7 16:38.507 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:37.462
Before features/support/hooks.rb:269 0.004
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 35.769
When I start Tails from USB drive "old" with network unplugged 1:55.673
Then the boot device has safe access rights 3.602
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:326 8.853
After features/support/hooks.rb:100 0.011
Tags: @product
2:30.274
Before features/support/hooks.rb:269 0.006
Given a computer 0.372
And I start Tails from USB drive "old" with network unplugged and I login 1:39.066
Then Tails is running from USB drive "old" 0.451
And I create a persistent partition 37.191
And I take note of which tps features are available 2.841
Then a Tails persistence partition exists on USB drive "old" 1.096
And I shutdown Tails and wait for the computer to power off 9.254
After features/support/hooks.rb:326 0.213
After features/support/hooks.rb:100 0.012
Tags: @product
3:16.501
Before features/support/hooks.rb:269 0.005
Given a computer 0.622
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.543
Then Tails is running from USB drive "old" 0.734
And all tps features are active 2.793
When I write some files expected to persist 2.722
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.567
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 2.660
And I take note of which tps features are available 0.711
And I shutdown Tails and wait for the computer to power off 6.437
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.274
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.010
Tags: @product
2:56.166
Before features/support/hooks.rb:269 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 13.460
And I log in to a new session 20.564
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.890
And I plug USB drive "to_upgrade" 2.503
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.087
Then the running Tails is installed on USB drive "to_upgrade" 31.225
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 7.191
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.221
Before features/support/hooks.rb:269 0.006
Given a computer 0.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.871
Then all tps features from the old Tails version are active 1.904
And Tails is running from USB drive "to_upgrade" 0.403
And the boot device has safe access rights 4.042
And the expected persistent files created with the old Tails version are present in the filesystem 1.807
And all persistent directories from the old Tails version have safe access rights 2.905
After features/support/hooks.rb:326 0.921
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
2:32.765
Scenario Upgrading an initial Tails installation with an incremental upgrade
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 19.193
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.382
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.090
And Tor is ready 22.308
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1:49.855
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:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 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 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.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.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 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 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:326 6.384 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:46:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/2/artifact/build-artifacts/01:46:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/2/artifact/build-artifacts/01:46:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/2/artifact/build-artifacts/01:46:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/2/artifact/build-artifacts/01:46:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
13.115
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 12.601
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.110
Command 
Command failed: sudo -u tails-upgrade-frontend gpg --batch --list-keys --with-colons A490D0F4D311A4153E2BB7CADBB802B258ACD84F
error code: 2
stdout: tru::1:1734529000:0:3:1:5

stderr: gpg: directory '/var/lib/tails-upgrade-frontend/.gnupg' created
gpg: keybox '/var/lib/tails-upgrade-frontend/.gnupg/pubring.kbx' created
gpg: /var/lib/tails-upgrade-frontend/.gnupg/trustdb.gpg: trustdb created
gpg: error reading key: No public key
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:483:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:480:in `execute_successfully'
./features/step_definitions/usb.rb:1393:in `upgrader_trusted_signing_subkeys'
./features/step_definitions/usb.rb:1402: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.547 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:47:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20701-migrate-away-from-moox-late/2/artifact/build-artifacts/01:47:15_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/2/artifact/build-artifacts/01:47:15_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/2/artifact/build-artifacts/01:47:15_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/2/artifact/build-artifacts/01:47:15_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000