Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 10 29 Oct 2024, 18:48

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:32.002 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:19.792
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 34.374
When I start Tails from USB drive "old" with network unplugged 1:39.749
Then the boot device has safe access rights 3.267
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:326 4.016
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.543
Before features/support/hooks.rb:269 0.004
Given a computer 1.521
And I start Tails from USB drive "old" with network unplugged and I login 1:40.663
Then Tails is running from USB drive "old" 0.504
And I create a persistent partition 33.305
And I take note of which tps features are available 2.075
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.700
After features/support/hooks.rb:326 0.204
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.975
Before features/support/hooks.rb:269 0.004
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.212
Then Tails is running from USB drive "old" 0.609
And all tps features are active 2.325
When I write some files expected to persist 1.875
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.540
And all persistent directories from the old Tails version have safe access rights 2.815
And I take note of which tps features are available 0.609
And I shutdown Tails and wait for the computer to power off 4.374
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.126
After features/support/hooks.rb:326 0.104
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.373
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 26.511
And I log in to a new session 19.228
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.687
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.373
Then the running Tails is installed on USB drive "to_upgrade" 27.653
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.271
After features/support/hooks.rb:326 2.185
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.520
Before features/support/hooks.rb:269 0.005
Given a computer 0.318
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.536
Then all tps features from the old Tails version are active 1.717
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.276
And the expected persistent files created with the old Tails version are present in the filesystem 1.845
And all persistent directories from the old Tails version have safe access rights 2.475
After features/support/hooks.rb:326 0.718
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:59.243
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 16.877
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.129
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.096
And Tor is ready 24.348
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.449
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.131
Given I shutdown Tails and wait for the computer to power off 13.107
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.490
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.362
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.326
When the network is plugged 0.065
And Tor is ready 17.473
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.132
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.275
Given I shutdown Tails and wait for the computer to power off 4.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.852
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.236
And the file system changes introduced in version 6.3~testoverlayfs are present 0.575
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.425
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.507
When the network is plugged 0.336
And Tor is ready 20.169
Then the Upgrader considers the system as up-to-date 10.964
# 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.299
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.756
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.552
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 10.413
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 1.007
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 20.679
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.941
After features/support/hooks.rb:326 0.698
After features/support/hooks.rb:100 0.000