Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 4 16 Dec 2024, 18:27

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:38.549 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:50.661
Before features/support/hooks.rb:269 0.006
Given a computer 0.333
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 1:7.397
When I start Tails from USB drive "old" with network unplugged 1:37.660
Then the boot device has safe access rights 3.084
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 7.048
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.249
Before features/support/hooks.rb:269 0.007
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login 1:28.130
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 31.503
And I take note of which tps features are available 1.802
Then a Tails persistence partition exists on USB drive "old" 0.990
And I shutdown Tails and wait for the computer to power off 9.219
After features/support/hooks.rb:326 0.207
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.015
Before features/support/hooks.rb:269 0.008
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.039
Then Tails is running from USB drive "old" 1.048
And all tps features are active 2.527
When I write some files expected to persist 2.183
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.528
And all persistent directories from the old Tails version have safe access rights 2.621
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.266
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.891
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.034
Tags: @product
2:36.467
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.277
And I log in to a new session 20.902
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.104
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.659
Then the running Tails is installed on USB drive "to_upgrade" 22.647
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.256
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.910
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.816
Then all tps features from the old Tails version are active 1.825
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.718
And the expected persistent files created with the old Tails version are present in the filesystem 1.443
And all persistent directories from the old Tails version have safe access rights 2.555
After features/support/hooks.rb:326 1.012
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:48.320
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 12.620
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.489
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.533
When the network is plugged 0.067
And Tor is ready 21.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.873
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.458
Given I shutdown Tails and wait for the computer to power off 8.873
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.536
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.473
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.420
When the network is plugged 0.089
And Tor is ready 19.489
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.039
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.603
Given I shutdown Tails and wait for the computer to power off 4.532
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.615
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.024
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.069
And Tor is ready 20.225
Then the Upgrader considers the system as up-to-date 0.309
# 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.934
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.991
After features/support/hooks.rb:326 0.786
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
39.924
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 9.960
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.456
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the signing key used by the Upgrader is outdated 0.955
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 21.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.504
After features/support/hooks.rb:326 0.666
After features/support/hooks.rb:100 0.000