QA:Testcase upgrade dnf previous server domain controller

Associated release criterion
This test case is associated with the Fedora_41_Beta_Release_Criteria#Server-upgrade-requirements release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.

Description

This tests upgrading from the previous Server release (presently Fedora 39) to the next release (presently Fedora 41) configured as a FreeIPA domain controller, using DNF system upgrade.

Setup

1. Perform an installation of Fedora 39 with default partitioning.
2. Do a full system update and reboot.
3. Follow QA:Testcase_freeipa_trust_server_installation to set up the system as a FreeIPA domain controller.
4. Ideally, also deploy one or more Fedora 39 clients, via the realm CLI, kickstart and/or cockpit.

How to test

1. Install the latest stable version of dnf-plugin-system-upgrade package:

   sudo dnf install --best --refresh dnf-plugin-system-upgrade

2. Download the updates:

   sudo dnf system-upgrade download --refresh --releasever=41

   • You can change 41 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)

Upgrade clients now
If also testing clients, upgrade those in the same way once the server has upgraded.

Expected Results

1. The upgrade tool should run to completion without an 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. If the original system had an encrypted storage, there should be no problem accessing encrypted storage in the upgraded system as well.
5. The upgraded system should meet all relevant Fedora Release Criteria.
6. The upgraded system should meet all expected results in the server deployment test case.
7. Any upgraded clients must meet all expected results in the relevant client deployment test case.