Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 21 08 Nov 2024, 18:07

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 18:27.546 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:4.057
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.648
When I start Tails from USB drive "old" with network unplugged 1:27.150
Then the boot device has safe access rights 2.941
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:326 3.570
After features/support/hooks.rb:100 0.007
Tags: @product
2:4.985
Before features/support/hooks.rb:269 0.003
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:21.351
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 32.538
And I take note of which tps features are available 1.411
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 8.407
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.570
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.448
Then Tails is running from USB drive "old" 0.326
And all tps features are active 1.968
When I write some files expected to persist 1.847
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.252
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.333
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.162
After features/support/hooks.rb:326 0.098
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.753
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 11.488
And I log in to a new session 19.622
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.602
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.411
Then the running Tails is installed on USB drive "to_upgrade" 17.640
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.333
After features/support/hooks.rb:326 7.668
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.903
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.494
Then all tps features from the old Tails version are active 1.617
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.207
And the expected persistent files created with the old Tails version are present in the filesystem 1.722
And all persistent directories from the old Tails version have safe access rights 2.327
After features/support/hooks.rb:326 0.636
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:10.011
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.421
And no SquashFS delta is installed 0.203
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.079
And Tor is ready 20.766
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.135
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.707
Given I shutdown Tails and wait for the computer to power off 8.440
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.305
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.987
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.303
When the network is plugged 0.077
And Tor is ready 18.744
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.555
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.611
Given I shutdown Tails and wait for the computer to power off 6.362
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.563
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.097
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.089
And Tor is ready 19.071
Then the Upgrader considers the system as up-to-date 0.303
# 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.198
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.903
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.263
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 9.448
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.420
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.830
But a current signing key is available on our website 0.000
When the network is plugged 0.156
And Tor is ready 19.012
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.340
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.000