Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 25 13 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 19:15.518 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:12.253
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 28.427
When I start Tails from USB drive "old" with network unplugged 1:38.156
Then the boot device has safe access rights 3.057
And Tails is running from USB drive "old" 0.495
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.139
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.274
After features/support/hooks.rb:326 3.591
After features/support/hooks.rb:100 0.021
Tags: @product
2:6.150
Before features/support/hooks.rb:269 0.006
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:23.968
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 32.421
And I take note of which tps features are available 1.430
Then a Tails persistence partition exists on USB drive "old" 0.709
And I shutdown Tails and wait for the computer to power off 7.063
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.052
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.429
Then Tails is running from USB drive "old" 1.604
And all tps features are active 2.540
When I write some files expected to persist 1.945
# 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.376
And all persistent directories from the old Tails version have safe access rights 3.221
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.442
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.572
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.192
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 10.823
And I log in to a new session 20.651
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.532
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.917
Then the running Tails is installed on USB drive "to_upgrade" 21.392
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 2.521
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.424
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.906
Then all tps features from the old Tails version are active 1.595
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.467
And the expected persistent files created with the old Tails version are present in the filesystem 1.425
And all persistent directories from the old Tails version have safe access rights 2.484
After features/support/hooks.rb:326 0.727
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:24.914
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.376
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.075
And Tor is ready 24.052
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.357
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.314
Given I shutdown Tails and wait for the computer to power off 8.708
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.294
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.192
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.287
When the network is plugged 0.112
And Tor is ready 18.410
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.489
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.362
Given I shutdown Tails and wait for the computer to power off 4.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.308
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.229
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
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.411
When the network is plugged 0.074
And Tor is ready 17.750
Then the Upgrader considers the system as up-to-date 0.389
# 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.474
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.072
After features/support/hooks.rb:326 0.772
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
39.529
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 9.787
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.860
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 21.749
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.626
After features/support/hooks.rb:326 0.657
After features/support/hooks.rb:100 0.000