Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 2 14 Dec 2024, 19:13

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:31.754 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:25.715
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 33.735
When I start Tails from USB drive "old" with network unplugged 1:46.260
Then the boot device has safe access rights 3.337
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 3.519
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.877
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:31.508
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 31.753
And I take note of which tps features are available 1.911
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.291
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.183
Before features/support/hooks.rb:269 0.005
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.314
Then Tails is running from USB drive "old" 1.244
And all tps features are active 2.217
When I write some files expected to persist 1.923
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 4.270
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.261
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.565
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.086
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 13.848
And I log in to a new session 23.356
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.040
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.223
Then the running Tails is installed on USB drive "to_upgrade" 23.671
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.293
After features/support/hooks.rb:326 2.124
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.193
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.316
Then all tps features from the old Tails version are active 1.826
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 4.404
And the expected persistent files created with the old Tails version are present in the filesystem 1.509
And all persistent directories from the old Tails version have safe access rights 2.600
After features/support/hooks.rb:326 0.747
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:52.060
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.312
And no SquashFS delta is installed 0.101
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.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.423
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.086
And Tor is ready 21.602
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.079
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.375
Given I shutdown Tails and wait for the computer to power off 8.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.715
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.625
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
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.291
# 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.314
When the network is plugged 0.079
And Tor is ready 20.163
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.836
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.498
Given I shutdown Tails and wait for the computer to power off 4.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.744
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 4.733
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.358
When the network is plugged 0.151
And Tor is ready 19.813
Then the Upgrader considers the system as up-to-date 0.356
# 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.023
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.037
After features/support/hooks.rb:326 0.787
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
54.637
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 25.832
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.964
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 1.018
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 19.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.880
After features/support/hooks.rb:326 0.698
After features/support/hooks.rb:100 0.000