QA:Testcase upgrade fedup cli previous desktop
From FedoraProject
(Difference between revisions)
m (fixing command to get to the bottom of journalctl output) |
(easier way to see the progress) |
||
| Line 19: | Line 19: | ||
# Once the system reboots, there should be a new entry in the GRUB menu titled {{command|System Upgrade}}. | # 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 | # Select the {{command|System Upgrade}} option from the GRUB menu | ||
| − | #* If you want to be able to see progress during the upgrade, append | + | #* If you want to be able to see progress during the upgrade, append <code>plymouth.splash=fedup</code> to the end of the kernel parameters |
| − | # The system should boot into the upgrade process and a | + | # The system should boot into the upgrade process and a fedup progress screen should be displayed |
| − | #* | + | #* Do not press any key, otherwise the progress screen will be killed and you will have no information about the process |
| − | + | ||
| − | + | ||
# Once the upgrade process has completed, the system will reboot and an option to boot {{FedoraVersion|long|next}} will be on the grub menu | # 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. | # Log in to upgraded system, open a terminal, file browser, or other system applications. | ||
Revision as of 10:21, 28 November 2012
Description
This case is for upgrading using to upgrade the current release (Fedora 18) to the branched release (Fedora 19) using the Fedup CLI.
How to test
- Perform an installation of the stable release (e.g. Fedora 18) with default partitioning (no less than 500MB for
/boot), selecting the default package set. - Do a full system update and reboot
- Install
fedup- Be sure to get the latest release, this may involve enabling updates-testing (put
--enablerepo=updates-testingbetweenyumandinstallon the command line) - 2012-11-22: Make sure you have at least fedup-0.7.1-1.fc17.
- Be sure to get the latest release, this may involve enabling updates-testing (put
- 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 ...)
- 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
-
- Check the
fedupdebug.logfile if any errors show up in the output fromfedup-cli - Reboot the system if
fedup-clihas completed without error. - Once the system reboots, there should be a new entry in the GRUB menu titled
System Upgrade. - Select the
System Upgradeoption from the GRUB menu- If you want to be able to see progress during the upgrade, append
plymouth.splash=fedupto the end of the kernel parameters
- If you want to be able to see progress during the upgrade, append
- The system should boot into the upgrade process and a fedup progress screen should be displayed
- Do not press any key, otherwise the progress screen will be killed and you will have no information about the process
- Once the upgrade process has completed, the system will reboot and an option to boot Fedora 19 will be on the grub menu
- Log in to upgraded system, open a terminal, file browser, or other system applications.
Expected Results
-
fedup-cliwill run to completion, without error - The upgrade process should complete and reboot without user assistance beyond selecting
System Upgradefrom the GRUB menu - The system should be upgraded to new version without error.
- The opened terminal, file browser, or other system applications should display and work correctly.
- Running through the desktop test cases would be a good for verification.