Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 3 25 Oct 2024, 18:44

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 44 2 41 0 0 87 5 2 7 13:42.438 Failed
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:11.828
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.657
When I start Tails from USB drive "old" with network unplugged 1:35.670
Then the boot device has safe access rights 3.165
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.751
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.815
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:27.820
Then Tails is running from USB drive "old" 0.401
And I create a persistent partition 33.801
And I take note of which tps features are available 1.504
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.284
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.600
Before features/support/hooks.rb:269 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.291
Then Tails is running from USB drive "old" 1.105
And all tps features are active 2.049
When I write some files expected to persist 3.031
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.675
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.458
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.685
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.561
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.333
And I log in to a new session 21.303
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.783
And I plug USB drive "to_upgrade" 2.528
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.151
Then the running Tails is installed on USB drive "to_upgrade" 20.999
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:326 3.211
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.756
Before features/support/hooks.rb:269 0.009
Given a computer 0.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.173
Then all tps features from the old Tails version are active 1.667
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.572
And the expected persistent files created with the old Tails version are present in the filesystem 1.317
And all persistent directories from the old Tails version have safe access rights 2.474
After features/support/hooks.rb:326 1.331
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
46.552
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 46.552
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./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:695:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:326 5.924 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:23:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/3/artifact/build-artifacts/01:23:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/3/artifact/build-artifacts/01:23:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/3/artifact/build-artifacts/01:23:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/3/artifact/build-artifacts/01:23:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
37.322
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 37.322
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./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:695:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:326 5.190 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:24:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/3/artifact/build-artifacts/01:24:11_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/3/artifact/build-artifacts/01:24:11_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/3/artifact/build-artifacts/01:24:11_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/3/artifact/build-artifacts/01:24:11_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000