Cucumber Reports (no 2) - Feature: Upgrading an old Tails USB installation

Project	Number	Date
test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring	2	04 Aug 2026, 11:25

	Steps	Scenarios	Features
Upgrading an old Tails USB installation	83	1	3	0	0	87	6	1	7	25:35.314	Failed

Tags: @product

1:16.769

Scenario Installing an old version of Tails to a pristine USB drive

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.002

Steps

Given a computer 0.057

And I create a 7200 MiB disk named "old" 0.007

And I plug USB drive "old" 1.020

And I write an old version of the Tails USB image to disk "old" 14.171

When I start Tails from USB drive "old" with network unplugged 57.997

Then the boot device has safe access rights 2.866

And Tails is running from USB drive "old" 0.239

And there is no persistence partition on USB drive "old" 0.050

And process "udev-watchdog" is running 0.060

And udev-watchdog is monitoring the correct device 0.173

And I unplug USB drive "old" 0.123

Hooks

After features/support/hooks.rb:339 3.860

After features/support/hooks.rb:108 0.090

Tags: @product

1:32.858

Scenario Creating a persistent partition with the old Tails USB installation

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.003

Steps

Given a computer 0.107

And I start Tails from USB drive "old" with network unplugged and I login 55.576

Then Tails is running from USB drive "old" 0.266

And I create a persistent partition 26.239

And I take note of which tps features are available 4.429

Then a Tails persistence partition exists on USB drive "old" 0.602

And I shutdown Tails and wait for the computer to power off 5.637

Hooks

After features/support/hooks.rb:339 0.565

After features/support/hooks.rb:108 0.008

Tags: @product

1:37.094

Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.002

Steps

Given a computer 0.068

And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.303

Then Tails is running from USB drive "old" 0.267

And all tps features are active 5.157

When I write some files expected to persist 1.447

# Verify that our baseline for the next scenarios is sane

And all persistent filesystems have safe access rights 0.198

And all persistence configuration files have safe access rights 0.341

And all persistent directories from the old Tails version have safe access rights 2.212

And I take note of which tps features are available 4.524

And I shutdown Tails and wait for the computer to power off 4.008

# 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" 12.565

Hooks

After features/support/hooks.rb:339 0.274

After features/support/hooks.rb:108 0.008

Tags: @product

15:33.936

Scenario Upgrading an old Tails USB installation from another Tails USB drive

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.004

Steps

Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.557

And I log in to a new session 13.762

And I clone USB drive "old" to a new USB drive "to_upgrade" 0.951

And I plug USB drive "to_upgrade" 2.246

When I upgrade Tails to USB drive "to_upgrade" by cloning 15:8.418

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendant of [application | ]: child with name='Information' roleName='alert'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:271:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/usb.rb:269:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:269:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_upgrade.feature:65:in `When I upgrade Tails to USB drive "to_upgrade" by cloning'

Then the running Tails is installed on USB drive "to_upgrade" 0.000

And I unplug USB drive "to_upgrade" 0.000

And I unplug USB drive "__internal" 0.000

Hooks

After features/support/hooks.rb:339 5.410

Output 1

SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 02:30:22)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/2/artifact/build-artifacts/02:30:22_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/2/artifact/build-artifacts/02:30:22_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/2/artifact/build-artifacts/02:30:22_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring/2/artifact/build-artifacts/02:30:22_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal

After features/support/hooks.rb:108 0.000

Tags: @product

1:16.105

Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.002

Steps

Given a computer 0.063

And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.586

Then all tps features from the old Tails version are active 0.983

And Tails is running from USB drive "to_upgrade" 0.267

And the boot device has safe access rights 2.606

And the expected persistent files created with the old Tails version are present in the filesystem 1.201

And all persistent directories from the old Tails version have safe access rights 2.396

Hooks

After features/support/hooks.rb:339 0.713

After features/support/hooks.rb:108 0.026

Tags: @product @automatic_upgrade

3:58.204

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.009

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.235

And no SquashFS delta is installed 0.076

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050

And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229

And the file system changes introduced in version 6.3~testoverlayfs are not present 0.300

When the network is plugged 0.017

And Tor is ready 12.928

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.350

And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.840

Given I shutdown Tails and wait for the computer to power off 6.923

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.126

Then Tails is running version 6.2~testoverlayfs 0.005

And all tps features are active 4.921

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.045

# Our IUK sets a release date that can make Tor bootstrapping impossible

Given Tails system time is magically synchronized 0.149

# 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.204

When the network is plugged 0.015

And Tor is ready 10.058

Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.395

And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.870

Given I shutdown Tails and wait for the computer to power off 4.211

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.076

Then Tails is running version 6.3~testoverlayfs 0.005

And all tps features are active 5.182

And the file system changes introduced in version 6.3~testoverlayfs are present 0.350

And only the 6.3~testoverlayfs SquashFS delta is installed 0.056

# 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.116

And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207

When the network is plugged 0.015

And Tor is ready 10.093

Then the Upgrader considers the system as up-to-date 10.624

# 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 4.412

And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.643

Hooks

After features/support/hooks.rb:339 0.923

After features/support/hooks.rb:108 0.028

Tags: @product @automatic_upgrade

20.345

Scenario Upgrading a Tails whose signing key is outdated

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.002

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.778

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216

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.045

But a current signing key is available on our website 0.000

When the network is plugged 0.013

And Tor is ready 9.700

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.502

Hooks

After features/support/hooks.rb:339 1.034

After features/support/hooks.rb:108 0.000

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Upgrading an old Tails USB installation	83	1	3	0	0	87	6	1	7	25:35.314	Failed

Feature Report