Project Number Date
test_Tails_ISO_21768-upgrade-chutney 1 16 Nov 2026, 19:07

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 11:46.922 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:11.544
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.733
When I start Tails from USB drive "old" with network unplugged 53.878
Then the boot device has safe access rights 2.025
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.746
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.299
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 49.214
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 23.744
And I take note of which tps features are available 7.247
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 4.186
After features/support/hooks.rb:339 0.547
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.798
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.555
Then Tails is running from USB drive "old" 0.256
And all tps features are active 7.518
When I write some files expected to persist 1.255
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 1.679
And I take note of which tps features are available 6.594
And I shutdown Tails and wait for the computer to power off 2.564
# 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.829
After features/support/hooks.rb:339 0.478
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.389
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.584
And I log in to a new session 12.793
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.744
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.062
Then the running Tails is installed on USB drive "to_upgrade" 18.708
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 2.217
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.456
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.260
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.946
Then all tps features from the old Tails version are active 1.134
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.018
And the expected persistent files created with the old Tails version are present in the filesystem 1.040
And all persistent directories from the old Tails version have safe access rights 1.834
After features/support/hooks.rb:339 0.809
After features/support/hooks.rb:108 0.006
3:46.793
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.659
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.317
When the network is plugged 0.037
And Tor is ready 13.262
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.532
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.910
Given I shutdown Tails and wait for the computer to power off 5.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.901
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.968
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.197
When the network is plugged 0.035
And Tor is ready 10.421
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.784
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.104
Given I shutdown Tails and wait for the computer to power off 4.137
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.226
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 10.523
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.037
And Tor is ready 10.564
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.645
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:339 1.121
After features/support/hooks.rb:108 0.015
19.639
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.690
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.661
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.954
After features/support/hooks.rb:339 0.588
After features/support/hooks.rb:108 0.000