Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 15 10 Nov 2024, 12:10

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 61 1 25 0 0 87 6 1 7 37:12.370 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:16.182
Before features/support/hooks.rb:269 0.004
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 33.425
When I start Tails from USB drive "old" with network unplugged 1:36.840
Then the boot device has safe access rights 3.478
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.565
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.968
Before features/support/hooks.rb:269 0.006
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login 1:30.369
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 31.986
And I take note of which tps features are available 2.101
Then a Tails persistence partition exists on USB drive "old" 0.928
And I shutdown Tails and wait for the computer to power off 8.948
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.011
Tags: @product
3:8.988
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.374
Then Tails is running from USB drive "old" 0.461
And all tps features are active 3.185
When I write some files expected to persist 2.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.307
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.768
And I take note of which tps features are available 0.810
And I shutdown Tails and wait for the computer to power off 4.500
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.859
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.308
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 11.813
And I log in to a new session 18.855
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.702
And I plug USB drive "to_upgrade" 2.577
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.289
Then the running Tails is installed on USB drive "to_upgrade" 27.553
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:326 2.709
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.351
Before features/support/hooks.rb:269 0.009
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.737
Then all tps features from the old Tails version are active 3.684
And Tails is running from USB drive "to_upgrade" 0.467
And the boot device has safe access rights 3.185
And the expected persistent files created with the old Tails version are present in the filesystem 1.373
And all persistent directories from the old Tails version have safe access rights 2.686
After features/support/hooks.rb:326 0.864
After features/support/hooks.rb:100 0.058
Tags: @product @automatic_upgrade
23:42.796
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.273
And no SquashFS delta is installed 0.216
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.076
And Tor is ready 21.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.986
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 22:56.204
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderDownloadComplete.png", "TailsUpgraderFailure.png"] on the screen (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:1320:in `/^I can successfully install the incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:91:in `And I can successfully install the incremental upgrade to version 6.2~testoverlayfs'
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 5.131 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:10:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/15/artifact/build-artifacts/02:10:22_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_20634-greeter-tps-update-failure-fix/15/artifact/build-artifacts/02:10:22_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/15/artifact/build-artifacts/02:10:22_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/15/artifact/build-artifacts/02:10:22_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
39.774
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.495
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.489
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.908
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 20.691
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.024
After features/support/hooks.rb:326 0.668
After features/support/hooks.rb:100 0.000