From Fedora Project Wiki

(fix url, remove Beta)
(corrected the URL to one that will actually work with the client, made some things more generic)
Line 9: Line 9:
#* Be sure to get the latest release, this may involve enabling updates-testing (put <code>--enablerepo=updates-testing</code> between {{command|yum}} and {{command|install}} on the command line)
#* Be sure to get the latest release, this may involve enabling updates-testing (put <code>--enablerepo=updates-testing</code> between {{command|yum}} and {{command|install}} on the command line)
#* '''2013-01-03: Make sure you have at least fedup-0.7.2-1.fc17.'''
#* '''2013-01-03: Make sure you have at least fedup-0.7.2-1.fc17.'''
# Find the URL of the branched TC or RC or updates.img under test. This URL should be of the form <nowiki>http://dl.fedoraproject.org/pub/alt/stage/18-<compose>/Fedora/<arch>/os</nowiki>.  The URL needs to point to the initrd.img and vmlinuz, but not necessarily all rpm packages.
# 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>
#* <compose> is the name of the compose under test (TC1, RC2 etc.)
#* <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 ...)
#* <arch> is the name of the arch running on the install to be upgraded (i386, x86_64 ...)
#* Due to the way that branced 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
# Start the upgrade prep by executing following command
#* {{command|sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo <URL>}}
#* {{command|sudo fedup-cli --network <version> --debuglog fedupdebug.log --instrepo <URL>}}
#* <URL> is the location found in the previous step  
#* <version> is the version of Fedora you are upgrading to (currently {{FedoraVersion||next}})
#* <URL> is the location found in the previous step
# To utilize a local mirror for the new arch Start the upgrade prep by executing following command
# To utilize a local mirror for the new arch Start the upgrade prep by executing following command
#* {{command|1=sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo <URL> --disablerepo=fedora --repourl fedora-local=<URL-LOCAL>}}
#* {{command|1=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
#* <URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds
# Check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}
# Check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}

Revision as of 14:48, 7 January 2013

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


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
    • Be sure to get the latest release, this may involve enabling updates-testing (put --enablerepo=updates-testing between yum and install on the command line)
    • 2013-01-03: Make sure you have at least fedup-0.7.2-1.fc17.
  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 branced 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
    • sudo 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. To utilize a local mirror for the new arch 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 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
    • If you want to be able to see progress during the upgrade, append plymouth.splash=fedup to the end of the kernel parameters
  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=316823"