Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 4 27 Oct 2024, 12:24

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:7.400 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:10.544
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.499
When I start Tails from USB drive "old" with network unplugged 1:32.580
Then the boot device has safe access rights 3.181
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.718
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.342
Before features/support/hooks.rb:269 0.003
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:21.781
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 34.483
And I take note of which tps features are available 1.486
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 8.259
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.403
Before features/support/hooks.rb:269 0.005
Given a computer 0.300
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.977
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.764
When I write some files expected to persist 1.687
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.330
And I take note of which tps features are available 0.478
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.614
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.990
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 11.129
And I log in to a new session 19.017
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.546
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.706
Then the running Tails is installed on USB drive "to_upgrade" 18.789
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 6.897
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.507
Before features/support/hooks.rb:269 0.018
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.297
Then all tps features from the old Tails version are active 1.553
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.226
And the expected persistent files created with the old Tails version are present in the filesystem 1.436
And all persistent directories from the old Tails version have safe access rights 2.461
After features/support/hooks.rb:326 0.963
After features/support/hooks.rb:100 0.007
6:36.876
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.218
And no SquashFS delta is installed 0.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.555
When the network is plugged 0.096
And Tor is ready 20.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.586
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.166
Given I shutdown Tails and wait for the computer to power off 11.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.501
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.310
And the file system changes introduced in version 6.2~testoverlayfs are present 0.445
And only the 6.2~testoverlayfs SquashFS delta is installed 0.118
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.342
When the network is plugged 0.067
And Tor is ready 21.336
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.148
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.098
Given I shutdown Tails and wait for the computer to power off 4.470
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.199
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.105
And the file system changes introduced in version 6.3~testoverlayfs are present 0.705
And only the 6.3~testoverlayfs SquashFS delta is installed 0.133
# 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.422
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.328
When the network is plugged 0.070
And Tor is ready 19.840
Then the Upgrader considers the system as up-to-date 0.329
# 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.026
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.931
After features/support/hooks.rb:326 0.819
After features/support/hooks.rb:100 0.014
36.735
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.586
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 1.149
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 16.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.956
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.000