QA:Testcase upgrade fedup cli previous desktop

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(cleaning up the URL formatting, changing verbage for package set and clarifying some variables in the upgrade URL)
m (reboot after update)
Line 5: Line 5:
 
|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
+
# Do a full system update and reboot
 
# Install {{package|fedup}}
 
# Install {{package|fedup}}
 
#* 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)

Revision as of 09:35, 22 November 2012

Important.png
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 20) to the branched release (Fedora 21) using the Fedup CLI.


How to test

  1. Perform an installation of the stable release (e.g. Fedora 20) with default partitioning (no less than 500MB for /boot), selecting the default package set.
  2. Do a full system update and reboot
  3. Install Package-x-generic-16.pngfedup
    • 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)
  4. Find the URL of the branched TC or RC under test. This URL should be of the form http://dl.fedoraproject.org/pub/alt/stage/18-Beta-<name>/Fedora/<arch>/os.
    • <name> is the name of the phase under test (Beta, Final etc.)
    • <arch> is the name of the arch running on the install to be upgraded (i386, x86_64 ...)
  5. Start the upgrade prep by executing following command
    • sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo <URL>
    • <URL> is the location found in the previous step
  6. Check the fedupdebug.log file if any errors show up in the output from fedup-cli
  7. Reboot the system if fedup-cli has completed without error.
  8. Once the system reboots, there should be a new entry in the GRUB menu titled System Upgrade.
  9. Select the System Upgrade option from the GRUB menu
    • If you want to be able to see progress during the upgrade, append rd.upgrade.debugshell to the end of the kernel parameters
  10. The system should boot into the upgrade process and a plymouth boot screen should be displayed
    • There may not be any output behind the plymouth splash, this doesn't mean that the upgrade stopped
    • If you enabled the debug shell, it will be available on VT2. You will need to wait until the upgrade process has completely started and type exit in order to access the upgrade environment.
    • Upgrade progress can be seen by using journalctl -a -o cat and scrolling to the bottom (Control+G will get you to the bottom if you don't want to scroll the whole way).
  11. Once the upgrade process has completed, the system will reboot and an option to boot Fedora 21 will be on the grub menu
  12. 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.