From Fedora Project Wiki
(clarify the expectations of this case and drop the inappropriate results (basic desktop functionality post-upgrade is not relevant to this test)) |
(obsolete test case - anaconda upgrades replaced with fedup) |
||
| Line 1: | Line 1: | ||
{{admon/note|Obsolete|As of Fedora 18, installer-based upgrades have been replaced by [[FedUp]]. See [[:Category:Package fedup test cases]].}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This case tests upgrading from the current stable release ({{FedoraVersion|long}}) to the development release ({{FedoraVersion|long|next}}) while '''updating''' the existing bootloader configuration. The intent of this option in anaconda is that the bootloader configuration file should be updated to list the new kernel installed with the upgrade, but the configuration file should not be re-created from scratch, nor should the actual bootloader itself be re-installed to the MBR or first sector of first partition. | |description=This case tests upgrading from the current stable release ({{FedoraVersion|long}}) to the development release ({{FedoraVersion|long|next}}) while '''updating''' the existing bootloader configuration. The intent of this option in anaconda is that the bootloader configuration file should be updated to list the new kernel installed with the upgrade, but the configuration file should not be re-created from scratch, nor should the actual bootloader itself be re-installed to the MBR or first sector of first partition. | ||
| Line 15: | Line 17: | ||
# The system should boot into the updated Fedora without error | # The system should boot into the updated Fedora without error | ||
}} | }} | ||
[[Category:Obsolete_Test_Cases]] | |||
[[Category: | |||
Revision as of 00:00, 8 July 2014
Obsolete
As of Fedora 18, installer-based upgrades have been replaced by FedUp. See Category:Package fedup test cases.
As of Fedora 18, installer-based upgrades have been replaced by FedUp. See Category:Package fedup test cases.
Description
This case tests upgrading from the current stable release (Fedora 41) to the development release (Fedora 42) while updating the existing bootloader configuration. The intent of this option in anaconda is that the bootloader configuration file should be updated to list the new kernel installed with the upgrade, but the configuration file should not be re-created from scratch, nor should the actual bootloader itself be re-installed to the MBR or first sector of first partition.
How to test
- Perform a default installation of the previous Fedora release (Fedora 41)
- Do a full system update
- Modify the bootloader configuration (e.g. grub.conf, yaboot.conf, elilo.conf or zipl.conf depending on your platform). Append several useless kernel arguments and increase the boot timeout. You're looking to make enough changes that you can verify they remain after the upgrade. For example, considering adding a kernel boot arguments:
TESTING=cool ABC. - Boot the Fedora 42 installer using any available means (
boot.iso, PXE orDVD.iso) - After anaconda is started successfully, select default language, keyboard, and then select Upgrade an existing installation
- Select Update boot loader configuration to upgrade
- After upgrade finished, reboot the system
- Examine the bootloader configuration file and check whether your previous customizations are still present
Expected Results
- The system should be upgraded to Fedora 42 version without error
- The bootloader configuration changes should be present in the upgraded system
- The system should boot into the updated Fedora without error