Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 26 14 Nov 2024, 18:09

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 19:47.716 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:3.335
Before features/support/hooks.rb:269 0.005
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.425
When I start Tails from USB drive "old" with network unplugged 1:26.354
Then the boot device has safe access rights 3.198
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 3.760
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.448
Before features/support/hooks.rb:269 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:33.521
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 32.344
And I take note of which tps features are available 1.260
Then a Tails persistence partition exists on USB drive "old" 0.857
And I shutdown Tails and wait for the computer to power off 8.893
After features/support/hooks.rb:326 0.202
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.850
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.143
Then Tails is running from USB drive "old" 1.031
And all tps features are active 1.969
When I write some files expected to persist 2.249
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 3.339
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.338
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.428
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.737
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.994
And I log in to a new session 20.038
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.853
And I plug USB drive "to_upgrade" 2.382
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.362
Then the running Tails is installed on USB drive "to_upgrade" 23.609
And I unplug USB drive "to_upgrade" 0.259
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:326 1.955
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.583
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.623
Then all tps features from the old Tails version are active 1.913
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.606
And the expected persistent files created with the old Tails version are present in the filesystem 1.426
And all persistent directories from the old Tails version have safe access rights 2.486
After features/support/hooks.rb:326 1.080
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:4.701
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 13.327
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.440
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.076
And Tor is ready 28.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.096
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.975
Given I shutdown Tails and wait for the computer to power off 11.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.811
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.367
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.279
When the network is plugged 0.101
And Tor is ready 17.663
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.536
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.519
Given I shutdown Tails and wait for the computer to power off 4.483
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.323
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.149
And the file system changes introduced in version 6.3~testoverlayfs are present 0.701
And only the 6.3~testoverlayfs SquashFS delta is installed 0.115
# 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.496
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.530
When the network is plugged 0.075
And Tor is ready 17.617
Then the Upgrader considers the system as up-to-date 0.324
# 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 13.689
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.202
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
43.058
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.014
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.756
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.911
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 23.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.523
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.000