Project Number Date
test_Tails_ISO_21769-fix-chutney-configure-freeze 2 01 Oct 2026, 01:57

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 10:54.174 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:15.132
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.121
When I start Tails from USB drive "old" with network unplugged 58.797
Then the boot device has safe access rights 1.624
And Tails is running from USB drive "old" 0.132
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.146
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.385
After features/support/hooks.rb:108 0.063
Tags: @product
1:20.172
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 46.633
Then Tails is running from USB drive "old" 0.156
And I create a persistent partition 23.053
And I take note of which tps features are available 5.821
Then a Tails persistence partition exists on USB drive "old" 0.478
And I shutdown Tails and wait for the computer to power off 3.950
After features/support/hooks.rb:339 0.133
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.696
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.853
Then Tails is running from USB drive "old" 0.198
And all tps features are active 7.098
When I write some files expected to persist 1.011
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.098
And all persistence configuration files have safe access rights 0.199
And all persistent directories from the old Tails version have safe access rights 1.520
And I take note of which tps features are available 5.753
And I shutdown Tails and wait for the computer to power off 2.509
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.378
After features/support/hooks.rb:339 0.596
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.310
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.924
And I log in to a new session 11.599
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.983
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.635
Then the running Tails is installed on USB drive "to_upgrade" 17.735
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.535
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.611
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.795
Then all tps features from the old Tails version are active 0.910
And Tails is running from USB drive "to_upgrade" 0.159
And the boot device has safe access rights 2.076
And the expected persistent files created with the old Tails version are present in the filesystem 0.905
And all persistent directories from the old Tails version have safe access rights 1.685
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:17.071
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.992
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.300
When the network is plugged 0.025
And Tor is ready 12.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.294
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.283
Given I shutdown Tails and wait for the computer to power off 5.161
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.822
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.125
And the file system changes introduced in version 6.2~testoverlayfs are present 0.140
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.095
# 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.182
When the network is plugged 0.028
And Tor is ready 9.983
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.288
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.412
Given I shutdown Tails and wait for the computer to power off 2.526
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.334
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.481
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.145
When the network is plugged 0.034
And Tor is ready 10.005
Then the Upgrader considers the system as up-to-date 0.080
# 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 3.242
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 0.717
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
18.179
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.720
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.190
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.971
After features/support/hooks.rb:339 0.939
After features/support/hooks.rb:108 0.000