Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 10 03 Nov 2024, 11:58

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:39.678 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.282
Before features/support/hooks.rb:269 0.004
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 35.830
When I start Tails from USB drive "old" with network unplugged 1:41.969
Then the boot device has safe access rights 3.091
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.247
After features/support/hooks.rb:326 3.774
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.179
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:30.012
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 34.965
And I take note of which tps features are available 2.094
Then a Tails persistence partition exists on USB drive "old" 0.877
And I shutdown Tails and wait for the computer to power off 8.691
After features/support/hooks.rb:326 0.197
After features/support/hooks.rb:100 0.008
Tags: @product
3:7.222
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.718
Then Tails is running from USB drive "old" 0.484
And all tps features are active 2.849
When I write some files expected to persist 2.081
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.487
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.892
And I take note of which tps features are available 0.776
And I shutdown Tails and wait for the computer to power off 4.515
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.748
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.877
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 11.155
And I log in to a new session 22.593
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.082
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.185
Then the running Tails is installed on USB drive "to_upgrade" 22.973
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.510
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.546
Before features/support/hooks.rb:269 0.005
Given a computer 0.348
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.516
Then all tps features from the old Tails version are active 2.060
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.863
And the expected persistent files created with the old Tails version are present in the filesystem 1.452
And all persistent directories from the old Tails version have safe access rights 2.927
After features/support/hooks.rb:326 0.912
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:50.616
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 15.352
And no SquashFS delta is installed 1.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
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.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.625
When the network is plugged 0.084
And Tor is ready 21.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.217
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.397
Given I shutdown Tails and wait for the computer to power off 11.610
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.982
Then Tails is running version 6.2~testoverlayfs 0.031
And all tps features are active 2.385
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.386
# 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.295
When the network is plugged 0.073
And Tor is ready 16.827
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.984
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.220
Given I shutdown Tails and wait for the computer to power off 4.437
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.331
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.543
And the file system changes introduced in version 6.3~testoverlayfs are present 0.546
And only the 6.3~testoverlayfs SquashFS delta is installed 0.135
# 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.412
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.416
When the network is plugged 0.096
And Tor is ready 19.012
Then the Upgrader considers the system as up-to-date 0.337
# 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 16.465
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.052
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
59.953
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.890
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
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 1.128
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 46.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
After features/support/hooks.rb:326 0.698
After features/support/hooks.rb:100 0.000