Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 35 23 Nov 2024, 18:28

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:49.968 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:9.824
Before features/support/hooks.rb:269 0.006
Given a computer 0.262
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 33.558
When I start Tails from USB drive "old" with network unplugged 1:30.488
Then the boot device has safe access rights 3.381
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 3.614
After features/support/hooks.rb:100 0.026
Tags: @product
2:6.896
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:23.711
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 31.461
And I take note of which tps features are available 1.748
Then a Tails persistence partition exists on USB drive "old" 0.902
And I shutdown Tails and wait for the computer to power off 8.471
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.689
Before features/support/hooks.rb:269 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.317
Then Tails is running from USB drive "old" 0.742
And all tps features are active 2.001
When I write some files expected to persist 1.824
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 3.067
And I take note of which tps features are available 0.554
And I shutdown Tails and wait for the computer to power off 4.292
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.992
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.016
Tags: @product
2:37.165
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.590
And I log in to a new session 20.092
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.709
And I plug USB drive "to_upgrade" 2.458
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.786
Then the running Tails is installed on USB drive "to_upgrade" 24.088
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 2.507
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.807
Before features/support/hooks.rb:269 0.004
Given a computer 1.442
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.557
Then all tps features from the old Tails version are active 3.158
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.738
And the expected persistent files created with the old Tails version are present in the filesystem 1.709
And all persistent directories from the old Tails version have safe access rights 2.790
After features/support/hooks.rb:326 0.710
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
6:53.124
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.627
And no SquashFS delta is installed 0.324
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.118
And Tor is ready 19.947
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.724
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.293
Given I shutdown Tails and wait for the computer to power off 13.145
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.292
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.253
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.343
# 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.299
When the network is plugged 0.089
And Tor is ready 20.989
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.425
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.239
Given I shutdown Tails and wait for the computer to power off 8.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.569
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.339
And the file system changes introduced in version 6.3~testoverlayfs are present 0.658
And only the 6.3~testoverlayfs SquashFS delta is installed 0.106
# 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.485
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.344
When the network is plugged 0.113
And Tor is ready 19.393
Then the Upgrader considers the system as up-to-date 0.343
# 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.995
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.176
After features/support/hooks.rb:326 0.899
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
42.460
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.944
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 23.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.420
After features/support/hooks.rb:326 0.869
After features/support/hooks.rb:100 0.000