Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 22 09 Nov 2024, 18:10

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:57.476 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:11.045
Before features/support/hooks.rb:269 0.003
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 31.495
When I start Tails from USB drive "old" with network unplugged 1:34.207
Then the boot device has safe access rights 3.065
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.519
After features/support/hooks.rb:100 0.007
Tags: @product
2:3.050
Before features/support/hooks.rb:269 0.003
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:21.069
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 30.659
And I take note of which tps features are available 1.655
Then a Tails persistence partition exists on USB drive "old" 0.767
And I shutdown Tails and wait for the computer to power off 8.382
After features/support/hooks.rb:326 0.122
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.717
Before features/support/hooks.rb:269 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.142
Then Tails is running from USB drive "old" 0.332
And all tps features are active 1.920
When I write some files expected to persist 2.018
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.532
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.334
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.134
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.491
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 10.395
And I log in to a new session 19.427
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.467
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.951
Then the running Tails is installed on USB drive "to_upgrade" 20.382
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 7.047
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.290
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.156
Then all tps features from the old Tails version are active 1.677
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 4.280
And the expected persistent files created with the old Tails version are present in the filesystem 1.426
And all persistent directories from the old Tails version have safe access rights 2.247
After features/support/hooks.rb:326 0.619
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:28.260
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 11.494
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.573
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.073
And Tor is ready 19.072
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.609
Given I shutdown Tails and wait for the computer to power off 1:17.725
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.088
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.090
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.245
When the network is plugged 0.072
And Tor is ready 19.815
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.443
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.887
Given I shutdown Tails and wait for the computer to power off 4.306
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.921
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.043
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.075
And Tor is ready 17.092
Then the Upgrader considers the system as up-to-date 0.297
# 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.248
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
35.619
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.772
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.551
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.743
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 19.274
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.148
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.000