Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 23 10 Nov 2024, 18:04

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:36.184 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
1:59.827
Before features/support/hooks.rb:269 0.003
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.108
When I start Tails from USB drive "old" with network unplugged 1:24.543
Then the boot device has safe access rights 2.957
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 7.200
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.161
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:22.767
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 33.501
And I take note of which tps features are available 1.328
Then a Tails persistence partition exists on USB drive "old" 0.858
And I shutdown Tails and wait for the computer to power off 8.145
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.646
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.205
Then Tails is running from USB drive "old" 0.344
And all tps features are active 2.280
When I write some files expected to persist 1.765
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 2.639
And I take note of which tps features are available 0.615
And I shutdown Tails and wait for the computer to power off 4.277
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.749
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.154
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 30.351
And I log in to a new session 20.009
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.890
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.009
Then the running Tails is installed on USB drive "to_upgrade" 21.894
And I unplug USB drive "to_upgrade" 0.379
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 3.803
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.115
Before features/support/hooks.rb:269 0.005
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.255
Then all tps features from the old Tails version are active 1.752
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.485
And the expected persistent files created with the old Tails version are present in the filesystem 1.597
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:326 0.645
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:43.390
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 30.368
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.427
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.100
And Tor is ready 23.576
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.346
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.623
Given I shutdown Tails and wait for the computer to power off 10.654
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.433
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.335
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.409
# 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.263
When the network is plugged 0.091
And Tor is ready 18.342
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.328
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.962
Given I shutdown Tails and wait for the computer to power off 4.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.119
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.088
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.087
And Tor is ready 19.780
Then the Upgrader considers the system as up-to-date 0.308
# 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.753
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.025
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.888
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 9.747
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.852
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 19.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.818
After features/support/hooks.rb:326 0.994
After features/support/hooks.rb:100 0.000