Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 1 13 Dec 2024, 20: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 19:32.003 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:14.139
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.643
When I start Tails from USB drive "old" with network unplugged 1:36.739
Then the boot device has safe access rights 3.371
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.095
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.571
After features/support/hooks.rb:100 0.011
Tags: @product
2:9.444
Before features/support/hooks.rb:269 0.008
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:26.543
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 31.202
And I take note of which tps features are available 1.694
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.599
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.489
Before features/support/hooks.rb:269 0.006
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.776
Then Tails is running from USB drive "old" 0.339
And all tps features are active 2.195
When I write some files expected to persist 1.768
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.773
And I take note of which tps features are available 0.423
And I shutdown Tails and wait for the computer to power off 4.268
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.149
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.685
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.452
And I log in to a new session 20.231
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.459
And I plug USB drive "to_upgrade" 2.450
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.332
Then the running Tails is installed on USB drive "to_upgrade" 22.322
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 6.891
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.189
Before features/support/hooks.rb:269 0.008
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.416
Then all tps features from the old Tails version are active 1.695
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.564
And the expected persistent files created with the old Tails version are present in the filesystem 1.423
And all persistent directories from the old Tails version have safe access rights 2.537
After features/support/hooks.rb:326 1.007
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:36.961
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 13.733
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.073
And Tor is ready 20.331
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.762
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.024
Given I shutdown Tails and wait for the computer to power off 8.977
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.132
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.054
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# 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.338
When the network is plugged 0.129
And Tor is ready 21.408
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.136
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.905
Given I shutdown Tails and wait for the computer to power off 4.676
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.291
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.034
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.335
When the network is plugged 0.142
And Tor is ready 16.754
Then the Upgrader considers the system as up-to-date 10.778
# 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.891
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.064
After features/support/hooks.rb:326 0.787
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.092
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 11.267
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.410
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 1.553
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 19.557
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.187
After features/support/hooks.rb:326 1.121
After features/support/hooks.rb:100 0.000