Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 6 18 Dec 2024, 18:32

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 22:7.615 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
3:15.187
Before features/support/hooks.rb:269 0.006
Given a computer 0.324
And I create a 7200 MiB disk named "old" 0.081
And I plug USB drive "old" 1.145
And I write an old version of the Tails USB image to disk "old" 1:23.942
When I start Tails from USB drive "old" with network unplugged 1:45.417
Then the boot device has safe access rights 3.213
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 3.787
After features/support/hooks.rb:100 0.012
Tags: @product
2:29.115
Before features/support/hooks.rb:269 0.009
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login 1:36.787
Then Tails is running from USB drive "old" 0.421
And I create a persistent partition 39.410
And I take note of which tps features are available 2.344
Then a Tails persistence partition exists on USB drive "old" 0.917
And I shutdown Tails and wait for the computer to power off 8.961
After features/support/hooks.rb:326 0.221
After features/support/hooks.rb:100 0.009
Tags: @product
3:19.523
Before features/support/hooks.rb:269 0.006
Given a computer 0.292
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:41.407
Then Tails is running from USB drive "old" 0.584
And all tps features are active 2.349
When I write some files expected to persist 1.813
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.645
And I take note of which tps features are available 0.488
And I shutdown Tails and wait for the computer to power off 4.198
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.033
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.012
Tags: @product
2:44.360
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.963
And I log in to a new session 25.964
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.863
And I plug USB drive "to_upgrade" 2.558
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.509
Then the running Tails is installed on USB drive "to_upgrade" 22.074
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 2.667
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.817
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.359
Then all tps features from the old Tails version are active 1.740
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.809
And the expected persistent files created with the old Tails version are present in the filesystem 1.564
And all persistent directories from the old Tails version have safe access rights 2.788
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.039
7:21.725
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 13.443
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.413
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.066
And Tor is ready 23.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.985
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.796
Given I shutdown Tails and wait for the computer to power off 10.904
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.077
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.622
And the file system changes introduced in version 6.2~testoverlayfs are present 0.471
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.307
When the network is plugged 0.090
And Tor is ready 45.840
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.675
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.640
Given I shutdown Tails and wait for the computer to power off 6.764
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.287
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.428
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.084
And Tor is ready 21.506
Then the Upgrader considers the system as up-to-date 0.349
# 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.268
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.792
After features/support/hooks.rb:326 0.805
After features/support/hooks.rb:100 0.024
42.885
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.798
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.821
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 20.625
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.140
After features/support/hooks.rb:326 0.857
After features/support/hooks.rb:100 0.000