From Fedora Project Wiki

(clean up somewhat and remove some of the hacks that aren't necessary any more)
(drop the admon)
Line 1: Line 1:
{{admon/important|Draft Test Case for New Software|This test case is very new and may still have errors. Fedup is also new software and this procedure may change. Please ask questions if anything is not clear and let us know if there are problems}}
{{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.

Revision as of 00:09, 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 fedup. It is usually a good idea to install the very latest version from updates-testing: {{{1}}}
  4. Find the URL of the development branch for Fedora 42. This URL should be of the form http://dl.fedoraproject.org/pub/fedora/linux/development/<version>/<arch>/os/
    • <version> is the of fedora under test (currently 42)
    • <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.
  5. Start the upgrade prep by executing following command
    • su -c 'fedup-cli --network <version> --debuglog fedupdebug.log --instrepo <URL>'
    • <version> is the version of Fedora you are upgrading to (currently 42)
    • <URL> is 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 following command:
    • sudo 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
  7. Check the fedupdebug.log file to see if any errors show up in the output from fedup-cli
  8. Reboot the system if fedup-cli has completed without error
  9. Once the system reboots, there should be a new entry in the GRUB menu titled System Upgrade
  10. Select the System Upgrade option from the GRUB menu
  11. 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" RHBZ #873144 and RHBZ #883075, exist for this and other previous display issues related to fedup. Remove this comment once the bugs are confirmed fixed
  12. Once the upgrade process has completed, the system will reboot and an option to boot Fedora 42 will be on the grub menu
  13. Log in to 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=326441"