(create new previous_workstation test case (covering 'previous stable', not 'current stable'))
(update per discussion on test list https://firstname.lastname@example.org/thread/OKP2DFFKV2AH6PAZV4K5OMKZXVTXNQKD/)
|Line 1:||Line 1:|
Latest revision as of 12:31, 12 June 2017
This tests upgrading from the previous Workstation release (presently Fedora 35) to the next release (presently Fedora 37) with the Workstation package set or a Live image using the DNF system upgrade.
- Perform an installation of Fedora Workstation 35 with default partitioning.
- Select the Workstation package set or use the Workstation Live image.
- Do a full system update and reboot.
How to test
- Install the latest stable version of
sudo dnf install --best --refresh dnf-plugin-system-upgrade
- Download the updates:
sudo dnf system-upgrade download --refresh --releasever=37
- You can change
37to 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.
- You can change
- 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.
- If downloading has completed without error, run:
sudo dnf system-upgrade reboot
- Once the system reboots, the system should boot into the upgrade process and a graphical progress screen should be displayed
- Pressing should switch from the graphical progress screen to the text progress information display
- Once the upgrade process has completed, the system should reboot and an option to boot the new release should be on the grub menu
- Log in to the upgraded system and test basic system applications (a terminal, file browser, or other, depending on the system flavor)
- The upgrade tool should run to completion without an error.
- The upgrade process should complete and reboot without user assistance.
- The system should be upgraded to the new release without error.
- If the original system had an encrypted storage, there should be no problem accessing encrypted storage in the upgraded system as well.
- The upgraded system should meet all relevant Fedora Release Criteria.