Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 9 29 Oct 2024, 02:42

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:31.292 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:13.218
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.338
When I start Tails from USB drive "old" with network unplugged 1:35.385
Then the boot device has safe access rights 3.136
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:326 3.742
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.796
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:27.456
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 32.513
And I take note of which tps features are available 2.036
Then a Tails persistence partition exists on USB drive "old" 0.935
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.827
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.790
Then Tails is running from USB drive "old" 0.752
And all tps features are active 2.173
When I write some files expected to persist 1.920
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.289
And all persistence configuration files have safe access rights 0.449
And all persistent directories from the old Tails version have safe access rights 2.462
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 4.240
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.065
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.011
Tags: @product
2:40.506
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 15.305
And I log in to a new session 20.764
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.817
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.732
Then the running Tails is installed on USB drive "to_upgrade" 23.050
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.597
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.609
Before features/support/hooks.rb:269 0.007
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.711
Then all tps features from the old Tails version are active 1.904
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.424
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.511
After features/support/hooks.rb:326 0.691
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:29.983
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.193
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.162
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.417
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.571
When the network is plugged 0.147
And Tor is ready 18.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.064
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.392
Given I shutdown Tails and wait for the computer to power off 11.336
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.534
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.469
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.415
# 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.335
When the network is plugged 0.077
And Tor is ready 17.858
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.074
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.931
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.494
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.524
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.066
And Tor is ready 18.128
Then the Upgrader considers the system as up-to-date 0.368
# 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.352
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.031
After features/support/hooks.rb:326 0.752
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
37.349
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 10.943
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.538
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.188
And the signing key used by the Upgrader is outdated 1.923
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 16.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.158
After features/support/hooks.rb:326 1.126
After features/support/hooks.rb:100 0.000