From Fedora Project Wiki

(Adamwill moved page QA:Testcase upgrade dnf previous workstation encrypted to QA:Testcase upgrade dnf current workstation encrypted: Align upgrade test case names with FedoraVersion template - http://lists.fedoraproject.org/archives/list/test@l...)
 
(create new previous_workstation_encrypted test case (covering 'previous stable', not 'current stable'))
Line 1: Line 1:
#REDIRECT [[QA:Testcase upgrade dnf current workstation encrypted]]
{{admon/warning|Name change: ''previous'' vs. ''current''|Until 2016-01-11, the test case at this location covered upgrades from the current stable Fedora release, not the previous stable Fedora release. On 2016-01-11 that test was renamed to [[QA:Testcase upgrade dnf current workstation encrypted]], and this test case was added. If you followed a link from a release validation result page created before 2016-01-11, please be aware that at the time the tests were run, this page more resembled [[QA:Testcase upgrade dnf current workstation encrypted]]. See [http://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/2O6KIAGOTRBT5FGBU5Y7QKW5YPIYJ5ZD/ this email] for more information.}}
 
{{Testcase upgrade|workstation|||encrypt|previous}}

Revision as of 22:42, 11 January 2016

Warning.png
Name change: previous vs. current
Until 2016-01-11, the test case at this location covered upgrades from the current stable Fedora release, not the previous stable Fedora release. On 2016-01-11 that test was renamed to QA:Testcase upgrade dnf current workstation encrypted, and this test case was added. If you followed a link from a release validation result page created before 2016-01-11, please be aware that at the time the tests were run, this page more resembled QA:Testcase upgrade dnf current workstation encrypted. See this email for more information.


Description

This test case tests upgrading from the previous release (presently Fedora Workstation 35) to the next release (presently Fedora Workstation 37) with disk encryption enabled using the dnf-plugin-system-upgrade CLI.


How to test

  1. Perform an installation of Fedora Workstation 35 with default partitioning (no less than 500MB for /boot) with encryption enabled on the INSTALLATION DESTINATION page.
  1. Install the latest stable version of Package-x-generic-16.pngdnf-plugin-system-upgrade package:
    sudo dnf install --best --refresh dnf-plugin-system-upgrade
  2. Download the updates:
    sudo dnf system-upgrade download --refresh --releasever=37
    • You can change 37 to test upgrading to a different Fedora release, of course.
    • If you need to use a local mirror to test a brand new change, you can enable it as normal, i.e. by adding --enablerepo=<name> option to the command line.
  3. To aid debugging, run this command to enable a root shell on VT9 during the upgrade boot:
    sudo systemctl add-wants system-update.target debug-shell.service

    If anything goes wrong during upgrade, you can live switch to VT9 and inspect current system state, logs, etc.

  4. If downloading has completed without error, run:
    sudo dnf system-upgrade reboot
  5. Once the system reboots, the system should boot into the upgrade process and a graphical progress screen should be displayed
    • Pressing Esc should switch from the graphical progress screen to the text progress information display
  6. Once the upgrade process has completed, the system should reboot and an option to boot the new release should be on the grub menu
  7. Log in to the upgraded system and test basic system applications (a terminal, file browser, or other, depending on the system flavor)

Expected Results

  1. dnf system-upgrade should run to completion, without error
  2. The upgrade process should complete and reboot without user assistance
  3. The system should be upgraded to the new release without error
  4. The upgraded system should meet all relevant Fedora Release Criteria
  5. Accessing the encrypted storage volume(s) should work normally after the upgrade


Important.png
Failures not related to encryption
If you encounter an issue that does not seem related to encryption, perform the test case that corresponds to this one without encryption, and verify the problem occurs in that case too. If so, consider it a failure of that test case, not this one.