From Fedora Project Wiki
(easier way to see the progress) |
(Add note about esc-kills-plymouth bug) |
||
Line 22: | Line 22: | ||
# The system should boot into the upgrade process and a fedup progress screen should be displayed | # 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 | #* Do not press any key, otherwise the progress screen will be killed and you will have no information about the process | ||
#** This is {{bz|873144}}, which should be fixed in builds containing fedup-dracut-0.7.2 or later. Remove this comment (and the one above) once the bug is 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 | # 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 16:05, 3 January 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
- 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. - 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-testing
betweenyum
andinstall
on 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.log
file if any errors show up in the output fromfedup-cli
- Reboot the system if
fedup-cli
has completed without error. - Once the system reboots, there should be a new entry in the GRUB menu titled
System Upgrade
. - 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
- 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
- This is RHBZ #873144, which should be fixed in builds containing fedup-dracut-0.7.2 or later. Remove this comment (and the one above) once the bug is confirmed fixed.
- 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 42 will be on the grub menu
- Log in to upgraded system, open a terminal, file browser, or other system applications.
Expected Results
fedup-cli
will run to completion, without error- The upgrade process should complete and reboot without user assistance beyond selecting
System Upgrade
from 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.