Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 33 21 Nov 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 18:52.927 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:4.110
Before features/support/hooks.rb:269 0.009
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.368
When I start Tails from USB drive "old" with network unplugged 1:28.179
Then the boot device has safe access rights 3.224
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 3.521
After features/support/hooks.rb:100 0.031
Tags: @product
2:8.033
Before features/support/hooks.rb:269 0.008
Given a computer 0.283
And I start Tails from USB drive "old" with network unplugged and I login 1:25.109
Then Tails is running from USB drive "old" 0.731
And I create a persistent partition 30.928
And I take note of which tps features are available 1.645
Then a Tails persistence partition exists on USB drive "old" 0.954
And I shutdown Tails and wait for the computer to power off 8.381
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.010
Tags: @product
2:49.906
Before features/support/hooks.rb:269 0.007
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.118
Then Tails is running from USB drive "old" 0.589
And all tps features are active 1.791
When I write some files expected to persist 1.574
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.490
And all persistent directories from the old Tails version have safe access rights 3.143
And I take note of which tps features are available 0.522
And I shutdown Tails and wait for the computer to power off 4.363
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.920
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.726
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.635
And I log in to a new session 19.534
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.091
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.684
Then the running Tails is installed on USB drive "to_upgrade" 21.945
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.152
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.943
Before features/support/hooks.rb:269 0.008
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.138
Then all tps features from the old Tails version are active 1.765
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.448
And the expected persistent files created with the old Tails version are present in the filesystem 1.488
And all persistent directories from the old Tails version have safe access rights 2.575
After features/support/hooks.rb:326 1.009
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:27.685
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.071
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.075
And Tor is ready 22.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.699
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.035
Given I shutdown Tails and wait for the computer to power off 10.699
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.320
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.398
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.269
When the network is plugged 0.071
And Tor is ready 20.078
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.657
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.276
Given I shutdown Tails and wait for the computer to power off 4.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.391
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.982
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.495
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.072
And Tor is ready 19.687
Then the Upgrader considers the system as up-to-date 0.311
# 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.804
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.047
After features/support/hooks.rb:326 0.823
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
37.520
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.003
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.064
And the signing key used by the Upgrader is outdated 0.786
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.698
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.000