From Fedora Project Wiki

(clean up some more)
(use a template for the upgrade procedure)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This case is for upgrading using to upgrade the current release ({{FedoraVersion|long}}) to the branched release ({{FedoraVersion|long|next}}) using the [https://github.com/wgwoods/fedup Fedup] CLI.
|description=This case is for upgrading using to upgrade the current release ({{FedoraVersion|long}}) to the branched release ({{FedoraVersion|long|next}}) using the [https://github.com/wgwoods/fedup Fedup] CLI.
|actions=
|actions=
# Perform an installation of the stable release (e.g. {{FedoraVersion|long}}) with default partitioning (no less than 500MB for {{filename|/boot}}), selecting the default package set.
# Perform an installation of the stable release (e.g. {{FedoraVersion|long}}) with default partitioning (no less than 500MB for {{filename|/boot}}), selecting the default package set.
# Do a full system update and reboot
{{fedup_upgrade_procedure}}
# Install {{package|fedup}}. It is usually a good idea to install the very latest version from ''updates-testing'': {{command|su -c 'yum --enablerepo<nowiki>=</nowiki>updates-testing install fedup'}}
# Find the URL of the development branch for {{FedoraVersion|long|next}}. This URL should be of the form <nowiki>http://dl.fedoraproject.org/pub/fedora/linux/development/<version>/<arch>/os/</nowiki>
#* <version> is the of fedora under test (currently {{FedoraVersion||next}})
#* <arch> is the name of the arch running on the install to be upgraded (i386, x86_64 ...)
#* Due to the way that branched composes are done, the fedup client is not capable of grabbing initrd and kernel from those branches. The devel branch will rebuild from whatever is in stable for every push to the devel stable branch.
# Start the upgrade prep by executing following command
#* {{command|su -c 'fedup-cli --network <version> --debuglog fedupdebug.log --instrepo <URL>'}}
#* <version> is the version of Fedora you are upgrading to (currently {{FedoraVersion||next}})
#* <URL> is the location found in the previous step
# If you need to use a local mirror to test a brand new change, start the upgrade prep by executing following command:
#* {{command|1=su -c 'fedup-cli --network <version> --debuglog fedupdebug.log --instrepo <URL> --disablerepo=fedora --repourl fedora-local=<URL-LOCAL>'}}
#* <URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds
# Check the {{filename|fedupdebug.log}} file to see if any errors show up in the output from {{command|fedup-cli}}
# Reboot the system if {{command|fedup-cli}} has completed without error
# Once the system reboots, there should be a new entry in the GRUB menu titled {{command|System Upgrade}}
# Select the {{command|System Upgrade}} option from the GRUB menu
# The system should boot into the upgrade process and a fedup progress screen should be displayed
#* Press the <ESC> key, will switch from the graphical progress screen to the textual progress information display
#** Returning to the graphical progress screen by pressing the <ESC> key will return you to a screen where the progress bar is "frozen" {{bz|873144}} and {{bz|883075}}, exist for this and other previous display issues related to fedup. Remove this comment once the bugs are confirmed fixed
# Once the upgrade process has completed, the system will reboot and an option to boot {{FedoraVersion|long|next}} will be on the grub menu
# Log in to upgraded system, open a terminal, file browser, or other system applications.
|results=
|results=
# {{command|fedup-cli}} will run to completion, without error
# {{command|fedup-cli}} will run to completion, without error

Revision as of 00:17, 15 March 2013

Description

This case is for upgrading using to upgrade the current release (Fedora 41) to the branched release (Fedora 42) using the Fedup CLI.


How to test

  1. Perform an installation of the stable release (e.g. Fedora 41) with default partitioning (no less than 500MB for /boot), selecting the default package set.
  2. Do a full system update and reboot
  3. Install the latest version of fedup from the stable or updates repository
  4. If you are doing pre-release testing, find the installation repository URL for the compose you are testing. If you are testing the current compose, the correct location should be https://kojipkgs.fedoraproject.org/mash/rawhide-20250110.n.0/rawhide/(arch)/os - replace (arch) with the correct arch
  5. Start the upgrade prep by executing:
    • sudo fedup --network <version> (--instrepo <URL>)
    • <version> is the version of Fedora you are upgrading to (currently 42)
    • If you are doing pre-release testing, include the --instrepo parameter, with <URL> as the location found in the previous step
  6. If you need to use a local mirror to test a brand new change, start the upgrade prep by executing the following command:
    • sudo fedup --network <version> --instrepo <URL> --disablerepo=fedora --repourl fedora-local=<URL-LOCAL>
    • <URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds
  7. Check /var/log/fedup.log file to see if any errors show up in the output from fedup
  8. Reboot the system if fedup has completed without error
  9. Once the system reboots, there should be a new entry in the boot menu titled System Upgrade
  10. Select the System Upgrade option from the boot menu
  11. The system should boot into the upgrade process and a fedup progress screen should be displayed
    • Pressing Esc should switch from the graphical progress screen to the text progress information display
  12. Once the upgrade process has completed, the system should reboot and an option to boot the new release should be on the grub menu
  13. Log in to the upgraded system, open a terminal, file browser, or other system applications.

Expected Results

  1. fedup-cli will run to completion, without error
  2. The upgrade process should complete and reboot without user assistance beyond selecting System Upgrade from the GRUB menu
  3. The system should be upgraded to new version without error
  4. The opened terminal, file browser, or other system applications should display and work correctly
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_upgrade_fedup_cli_previous_desktop&oldid=326446"