Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 11 04 Nov 2024, 11:59

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 21:22.911 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:21.108
Before features/support/hooks.rb:269 0.005
Given a computer 0.240
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" 32.420
When I start Tails from USB drive "old" with network unplugged 1:43.096
Then the boot device has safe access rights 3.182
And Tails is running from USB drive "old" 0.379
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.559
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.861
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:36.549
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 32.893
And I take note of which tps features are available 2.039
Then a Tails persistence partition exists on USB drive "old" 0.914
And I shutdown Tails and wait for the computer to power off 8.879
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
3:27.831
Before features/support/hooks.rb:269 0.007
Given a computer 1.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:41.973
Then Tails is running from USB drive "old" 0.457
And all tps features are active 4.225
When I write some files expected to persist 2.056
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.315
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 3.189
And I take note of which tps features are available 0.615
And I shutdown Tails and wait for the computer to power off 6.664
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.876
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.015
Tags: @product
2:51.223
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.482
And I log in to a new session 23.979
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.198
And I plug USB drive "to_upgrade" 2.519
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.426
Then the running Tails is installed on USB drive "to_upgrade" 19.783
And I unplug USB drive "to_upgrade" 0.361
And I unplug USB drive "__internal" 0.471
After features/support/hooks.rb:326 7.780
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.168
Before features/support/hooks.rb:269 0.006
Given a computer 0.750
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.733
Then all tps features from the old Tails version are active 2.059
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.610
And the expected persistent files created with the old Tails version are present in the filesystem 1.702
And all persistent directories from the old Tails version have safe access rights 2.899
After features/support/hooks.rb:326 1.139
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:1.080
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 28.408
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.430
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.638
When the network is plugged 0.089
And Tor is ready 22.785
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.647
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.973
Given I shutdown Tails and wait for the computer to power off 10.851
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.213
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.717
And the file system changes introduced in version 6.2~testoverlayfs are present 0.491
And only the 6.2~testoverlayfs SquashFS delta is installed 0.161
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.491
# 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.361
When the network is plugged 0.094
And Tor is ready 19.272
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.791
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.437
Given I shutdown Tails and wait for the computer to power off 6.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.118
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.301
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.445
When the network is plugged 0.087
And Tor is ready 18.308
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.063
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.992
After features/support/hooks.rb:326 0.849
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
42.637
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 13.727
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.204
And the signing key used by the Upgrader is outdated 0.999
But a current signing key is available on our website 0.000
When the network is plugged 0.399
And Tor is ready 18.606
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.491
After features/support/hooks.rb:326 1.658
After features/support/hooks.rb:100 0.000