Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 5 17 Dec 2024, 18:25

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 21:10.697 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:32.887
Before features/support/hooks.rb:269 0.006
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.089
And I write an old version of the Tails USB image to disk "old" 32.283
When I start Tails from USB drive "old" with network unplugged 1:54.496
Then the boot device has safe access rights 3.526
And Tails is running from USB drive "old" 0.399
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.130
And udev-watchdog is monitoring the correct device 0.375
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:326 3.842
After features/support/hooks.rb:100 0.013
Tags: @product
2:18.929
Before features/support/hooks.rb:269 0.008
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:31.614
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 34.854
And I take note of which tps features are available 1.954
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 9.012
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.011
Tags: @product
3:8.095
Before features/support/hooks.rb:269 0.007
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.724
Then Tails is running from USB drive "old" 1.735
And all tps features are active 2.340
When I write some files expected to persist 2.367
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 1.380
And all persistent directories from the old Tails version have safe access rights 2.764
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.552
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.285
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.407
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 26.614
And I log in to a new session 19.737
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.840
And I plug USB drive "to_upgrade" 2.541
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.771
Then the running Tails is installed on USB drive "to_upgrade" 23.355
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.298
After features/support/hooks.rb:326 3.620
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.123
Before features/support/hooks.rb:269 0.006
Given a computer 0.252
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:28.794
Then all tps features from the old Tails version are active 1.849
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.386
And the expected persistent files created with the old Tails version are present in the filesystem 1.808
And all persistent directories from the old Tails version have safe access rights 2.719
After features/support/hooks.rb:326 0.681
After features/support/hooks.rb:100 0.036
6:55.167
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 14.684
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.512
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.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.072
And Tor is ready 21.413
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.997
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.816
Given I shutdown Tails and wait for the computer to power off 11.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.365
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.410
And the file system changes introduced in version 6.2~testoverlayfs are present 0.403
And only the 6.2~testoverlayfs SquashFS delta is installed 0.108
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.474
# 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.438
When the network is plugged 0.095
And Tor is ready 20.623
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.221
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.341
Given I shutdown Tails and wait for the computer to power off 4.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.698
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.116
And the file system changes introduced in version 6.3~testoverlayfs are present 0.745
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.066
And Tor is ready 20.516
Then the Upgrader considers the system as up-to-date 0.344
# 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.880
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.112
After features/support/hooks.rb:326 0.759
After features/support/hooks.rb:100 0.021
42.085
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.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.531
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.887
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 22.212
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.251
After features/support/hooks.rb:326 0.700
After features/support/hooks.rb:100 0.000