Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 21 18 Nov 2024, 11:58

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:21.653 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:28.606
Before features/support/hooks.rb:269 0.004
Given a computer 1.009
And I create a 7200 MiB disk named "old" 0.693
And I plug USB drive "old" 1.233
And I write an old version of the Tails USB image to disk "old" 41.433
When I start Tails from USB drive "old" with network unplugged 1:39.732
Then the boot device has safe access rights 3.388
And Tails is running from USB drive "old" 0.396
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 3.597
After features/support/hooks.rb:100 0.038
Tags: @product
2:14.649
Before features/support/hooks.rb:269 0.005
Given a computer 0.319
And I start Tails from USB drive "old" with network unplugged and I login 1:27.017
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 34.847
And I take note of which tps features are available 2.117
Then a Tails persistence partition exists on USB drive "old" 0.993
And I shutdown Tails and wait for the computer to power off 8.992
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.569
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.130
Then Tails is running from USB drive "old" 1.896
And all tps features are active 2.951
When I write some files expected to persist 3.202
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 4.419
And I take note of which tps features are available 0.575
And I shutdown Tails and wait for the computer to power off 4.226
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.262
After features/support/hooks.rb:326 0.105
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.134
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 14.363
And I log in to a new session 20.790
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.487
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.521
Then the running Tails is installed on USB drive "to_upgrade" 20.903
And I unplug USB drive "to_upgrade" 0.342
And I unplug USB drive "__internal" 0.283
After features/support/hooks.rb:326 3.608
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.497
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.104
Then all tps features from the old Tails version are active 2.149
And Tails is running from USB drive "to_upgrade" 0.399
And the boot device has safe access rights 3.991
And the expected persistent files created with the old Tails version are present in the filesystem 1.604
And all persistent directories from the old Tails version have safe access rights 3.044
After features/support/hooks.rb:326 0.998
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:47.343
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.617
And no SquashFS delta is installed 0.777
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.541
When the network is plugged 0.083
And Tor is ready 25.885
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.475
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.718
Given I shutdown Tails and wait for the computer to power off 10.919
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.868
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.168
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.398
# 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.274
When the network is plugged 0.077
And Tor is ready 23.780
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.483
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.822
Given I shutdown Tails and wait for the computer to power off 6.755
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.691
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 4.522
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.390
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.332
And Tor is ready 20.165
Then the Upgrader considers the system as up-to-date 0.316
# 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.226
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.917
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
50.854
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 20.005
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.746
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 1.785
But a current signing key is available on our website 0.000
When the network is plugged 0.366
And Tor is ready 19.085
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.803
After features/support/hooks.rb:326 3.271
After features/support/hooks.rb:100 0.000