Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 2 25 Oct 2024, 14:49

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:4.964 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:23.652
Before features/support/hooks.rb:269 0.005
Given a computer 0.278
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 33.338
When I start Tails from USB drive "old" with network unplugged 1:44.437
Then the boot device has safe access rights 3.274
And Tails is running from USB drive "old" 0.409
And there is no persistence partition on USB drive "old" 0.102
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 7.180
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.408
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:26.740
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 33.194
And I take note of which tps features are available 1.562
Then a Tails persistence partition exists on USB drive "old" 0.915
And I shutdown Tails and wait for the computer to power off 8.450
After features/support/hooks.rb:326 0.260
After features/support/hooks.rb:100 0.012
Tags: @product
2:58.333
Before features/support/hooks.rb:269 0.007
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.656
Then Tails is running from USB drive "old" 0.409
And all tps features are active 2.488
When I write some files expected to persist 1.903
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.716
And I take note of which tps features are available 0.530
And I shutdown Tails and wait for the computer to power off 4.399
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.305
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.481
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 20.041
And I log in to a new session 19.168
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.080
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.871
Then the running Tails is installed on USB drive "to_upgrade" 23.438
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 4.520
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.474
Before features/support/hooks.rb:269 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.468
Then all tps features from the old Tails version are active 2.065
And Tails is running from USB drive "to_upgrade" 0.433
And the boot device has safe access rights 3.935
And the expected persistent files created with the old Tails version are present in the filesystem 1.484
And all persistent directories from the old Tails version have safe access rights 2.893
After features/support/hooks.rb:326 0.877
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:50.657
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.467
And no SquashFS delta is installed 0.557
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.385
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.071
And Tor is ready 23.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.072
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.839
Given I shutdown Tails and wait for the computer to power off 11.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.193
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.494
And the file system changes introduced in version 6.2~testoverlayfs are present 0.447
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.351
# 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.264
When the network is plugged 0.075
And Tor is ready 20.667
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.370
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.527
Given I shutdown Tails and wait for the computer to power off 4.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.682
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.355
And the file system changes introduced in version 6.3~testoverlayfs are present 0.584
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.415
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.061
And Tor is ready 19.291
Then the Upgrader considers the system as up-to-date 0.321
# 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.660
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.046
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.955
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.930
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.481
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 1.097
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 19.007
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.273
After features/support/hooks.rb:326 0.759
After features/support/hooks.rb:100 0.000