Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 7 28 Oct 2024, 21:14

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:18.029 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.585
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.273
When I start Tails from USB drive "old" with network unplugged 1:33.738
Then the boot device has safe access rights 3.255
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.096
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.741
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.193
Before features/support/hooks.rb:269 0.007
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login 1:25.017
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 33.275
And I take note of which tps features are available 1.841
Then a Tails persistence partition exists on USB drive "old" 0.866
And I shutdown Tails and wait for the computer to power off 6.608
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.590
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.112
Then Tails is running from USB drive "old" 0.336
And all tps features are active 2.053
When I write some files expected to persist 2.581
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.386
And I take note of which tps features are available 0.549
And I shutdown Tails and wait for the computer to power off 4.231
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.504
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.858
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.300
And I log in to a new session 22.775
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.401
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.016
Then the running Tails is installed on USB drive "to_upgrade" 20.498
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 2.741
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.457
Before features/support/hooks.rb:269 0.005
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.861
Then all tps features from the old Tails version are active 1.836
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 4.021
And the expected persistent files created with the old Tails version are present in the filesystem 1.625
And all persistent directories from the old Tails version have safe access rights 2.568
After features/support/hooks.rb:326 0.857
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:27.039
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.940
And no SquashFS delta is installed 0.282
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.636
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.086
And Tor is ready 19.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.869
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.070
Given I shutdown Tails and wait for the computer to power off 13.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.340
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.296
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.312
When the network is plugged 0.093
And Tor is ready 19.476
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.171
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.335
Given I shutdown Tails and wait for the computer to power off 4.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.128
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.421
And the file system changes introduced in version 6.3~testoverlayfs are present 0.580
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.537
When the network is plugged 0.074
And Tor is ready 19.591
Then the Upgrader considers the system as up-to-date 0.297
# 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.446
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.860
After features/support/hooks.rb:326 0.777
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
38.303
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 10.377
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.072
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.232
And the signing key used by the Upgrader is outdated 1.057
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 18.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.554
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.000