Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 29 17 Nov 2024, 18:11

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:47.111 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:9.155
Before features/support/hooks.rb:269 0.007
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.351
When I start Tails from USB drive "old" with network unplugged 1:29.479
Then the boot device has safe access rights 3.736
And Tails is running from USB drive "old" 0.408
And there is no persistence partition on USB drive "old" 0.122
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.265
After features/support/hooks.rb:326 7.041
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.297
Before features/support/hooks.rb:269 0.007
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:24.052
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 32.661
And I take note of which tps features are available 1.728
Then a Tails persistence partition exists on USB drive "old" 0.919
And I shutdown Tails and wait for the computer to power off 8.388
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.008
Tags: @product
3:1.137
Before features/support/hooks.rb:269 0.006
Given a computer 0.421
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.995
Then Tails is running from USB drive "old" 1.606
And all tps features are active 2.741
When I write some files expected to persist 2.836
# 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 1.612
And all persistent directories from the old Tails version have safe access rights 2.433
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 4.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.461
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.011
Tags: @product
2:46.798
Before features/support/hooks.rb:269 0.024
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.786
And I log in to a new session 23.499
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.350
And I plug USB drive "to_upgrade" 2.543
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.688
Then the running Tails is installed on USB drive "to_upgrade" 22.418
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.270
After features/support/hooks.rb:326 3.757
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.101
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.042
Then all tps features from the old Tails version are active 1.715
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.603
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 2.667
After features/support/hooks.rb:326 1.013
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:42.982
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.516
And no SquashFS delta is installed 0.682
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.108
And Tor is ready 23.481
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.651
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.354
Given I shutdown Tails and wait for the computer to power off 1:20.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.621
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.360
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.323
When the network is plugged 0.089
And Tor is ready 20.020
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.089
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.941
Given I shutdown Tails and wait for the computer to power off 4.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.342
Then Tails is running version 6.3~testoverlayfs 0.032
And all tps features are active 2.107
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.066
And Tor is ready 17.953
Then the Upgrader considers the system as up-to-date 0.314
# 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.794
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.795
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.638
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 10.951
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 1.036
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 20.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.530
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.000