Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 30 18 Nov 2024, 18:08

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 20:10.275 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:30.100
Before features/support/hooks.rb:269 0.008
Given a computer 0.255
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 35.492
When I start Tails from USB drive "old" with network unplugged 1:48.217
Then the boot device has safe access rights 3.358
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.802
After features/support/hooks.rb:326 13.920
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.568
Before features/support/hooks.rb:269 0.004
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:33.157
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 32.614
And I take note of which tps features are available 1.904
Then a Tails persistence partition exists on USB drive "old" 0.899
And I shutdown Tails and wait for the computer to power off 8.430
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.928
Before features/support/hooks.rb:269 0.006
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.099
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.387
When I write some files expected to persist 3.253
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.428
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 5.062
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.945
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.010
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 12.854
And I log in to a new session 23.031
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.786
And I plug USB drive "to_upgrade" 2.527
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.720
Then the running Tails is installed on USB drive "to_upgrade" 26.637
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:326 2.410
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.886
Before features/support/hooks.rb:269 0.022
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.550
Then all tps features from the old Tails version are active 2.507
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.406
And the expected persistent files created with the old Tails version are present in the filesystem 1.416
And all persistent directories from the old Tails version have safe access rights 2.494
After features/support/hooks.rb:326 0.652
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:30.052
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.151
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.069
And Tor is ready 23.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.982
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.336
Given I shutdown Tails and wait for the computer to power off 13.071
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.023
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.241
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# 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.296
When the network is plugged 0.060
And Tor is ready 16.930
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.874
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.636
Given I shutdown Tails and wait for the computer to power off 4.332
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.363
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.226
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.380
When the network is plugged 0.089
And Tor is ready 19.332
Then the Upgrader considers the system as up-to-date 0.341
# 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.972
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.000
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
41.728
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.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.623
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.824
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 22.322
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.535
After features/support/hooks.rb:326 1.576
After features/support/hooks.rb:100 0.000