Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 32 20 Nov 2024, 18:15

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:44.547 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:36.373
Before features/support/hooks.rb:269 0.005
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.596
When I start Tails from USB drive "old" with network unplugged 1:59.125
Then the boot device has safe access rights 3.252
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:326 3.815
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.601
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:26.359
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 37.255
And I take note of which tps features are available 2.149
Then a Tails persistence partition exists on USB drive "old" 1.029
And I shutdown Tails and wait for the computer to power off 9.238
After features/support/hooks.rb:326 0.213
After features/support/hooks.rb:100 0.012
Tags: @product
3:3.453
Before features/support/hooks.rb:269 0.007
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.044
Then Tails is running from USB drive "old" 1.135
And all tps features are active 2.932
When I write some files expected to persist 2.262
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.730
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 3.494
And I take note of which tps features are available 5.247
And I shutdown Tails and wait for the computer to power off 5.748
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.205
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.086
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 12.171
And I log in to a new session 20.859
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.910
And I plug USB drive "to_upgrade" 2.513
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.872
Then the running Tails is installed on USB drive "to_upgrade" 26.237
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.289
After features/support/hooks.rb:326 7.348
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.635
Before features/support/hooks.rb:269 0.005
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.359
Then all tps features from the old Tails version are active 1.780
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.777
And the expected persistent files created with the old Tails version are present in the filesystem 1.507
And all persistent directories from the old Tails version have safe access rights 2.604
After features/support/hooks.rb:326 0.690
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:43.118
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.443
And no SquashFS delta is installed 0.316
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.078
And Tor is ready 25.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.668
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.272
Given I shutdown Tails and wait for the computer to power off 11.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.379
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.357
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.221
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.901
# 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.551
When the network is plugged 0.099
And Tor is ready 19.951
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.639
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.614
Given I shutdown Tails and wait for the computer to power off 4.651
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.324
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.592
And the file system changes introduced in version 6.3~testoverlayfs are present 0.693
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.387
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.087
And Tor is ready 19.683
Then the Upgrader considers the system as up-to-date 0.334
# 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 15.271
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.100
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
1:5.279
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.871
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
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 1.223
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 49.087
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.615
After features/support/hooks.rb:326 1.070
After features/support/hooks.rb:100 0.000