Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 14 02 Nov 2024, 17:58

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 18:42.970 Passed
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:8.844
Before features/support/hooks.rb:269 0.004
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.523
When I start Tails from USB drive "old" with network unplugged 1:34.018
Then the boot device has safe access rights 3.038
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 7.066
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.887
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:22.035
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 30.570
And I take note of which tps features are available 1.578
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 8.417
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.017
Tags: @product
2:48.451
Before features/support/hooks.rb:269 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.775
Then Tails is running from USB drive "old" 0.385
And all tps features are active 1.940
When I write some files expected to persist 2.014
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.431
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.266
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.375
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.975
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 10.969
And I log in to a new session 21.768
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.722
And I plug USB drive "to_upgrade" 2.367
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.093
Then the running Tails is installed on USB drive "to_upgrade" 17.628
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 3.433
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.224
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.094
Then all tps features from the old Tails version are active 1.692
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.059
And the expected persistent files created with the old Tails version are present in the filesystem 1.403
And all persistent directories from the old Tails version have safe access rights 2.474
After features/support/hooks.rb:326 0.999
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:19.917
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.466
And no SquashFS delta is installed 0.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.610
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.491
When the network is plugged 0.931
And Tor is ready 19.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.564
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.217
Given I shutdown Tails and wait for the computer to power off 8.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.198
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.475
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
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.346
# 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.295
When the network is plugged 0.097
And Tor is ready 20.780
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.167
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.671
Given I shutdown Tails and wait for the computer to power off 4.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.087
Then Tails is running version 6.3~testoverlayfs 0.034
And all tps features are active 1.894
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.099
And Tor is ready 20.734
Then the Upgrader considers the system as up-to-date 0.296
# 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.319
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.108
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
35.669
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.367
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.822
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 20.027
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.994
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.000