From Fedora Project Wiki

(system update important to match release criteria)
(clarify the expectations of this case and drop the inappropriate results (basic desktop functionality post-upgrade is not relevant to this test))
Line 1: Line 1:
{{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.
|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.
|actions=
|actions=
# Perform a default installation of the previous Fedora release ({{FedoraVersion|long}})  
# Perform a default installation of the previous Fedora release ({{FedoraVersion|long}})  
Line 6: Line 6:
# 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: <code>TESTING=cool ABC</code>.
# 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: <code>TESTING=cool ABC</code>.
# Boot the {{FedoraVersion|long|next}} installer using any available means ({{filename|boot.iso}}, PXE or {{filename|DVD.iso}})   
# Boot the {{FedoraVersion|long|next}} installer using any available means ({{filename|boot.iso}}, PXE or {{filename|DVD.iso}})   
# After anaconda is started successfully, select default language,keyoard, and then select ''Upgrade an existing installation''
# After anaconda is started successfully, select default language, keyboard, and then select ''Upgrade an existing installation''
# Select '''Update boot loader configuration''' to upgrade
# Select '''Update boot loader configuration''' to upgrade
# After upgrade finished, reboot the system
# After upgrade finished, reboot the system
# Login upgraded system and perform some basic desktop operations
# Examine the bootloader configuration file and check whether your previous customizations are still present
#* Open a terminal
#* Open file browser
#* or other system applications
|results=
|results=
# The system should be upgraded to {{FedoraVersion|long|next}} version without error
# The system should be upgraded to {{FedoraVersion|long|next}} version without error
# The bootloader configuration changes are present in the upgraded system
# The bootloader configuration changes should be present in the upgraded system
# The system can boot into new version fedora without error
# The system should boot into the updated Fedora without error
# The opened terminal, file browser, or other system applications should display and work correctly
}}
}}


[[Category:Upgrade_system]]
[[Category:Upgrade_system]]

Revision as of 02:13, 8 December 2011

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

  1. Perform a default installation of the previous Fedora release (Fedora 41)
  2. Do a full system update
  3. 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.
  4. Boot the Fedora 42 installer using any available means (boot.iso, PXE or DVD.iso)
  5. After anaconda is started successfully, select default language, keyboard, and then select Upgrade an existing installation
  6. Select Update boot loader configuration to upgrade
  7. After upgrade finished, reboot the system
  8. Examine the bootloader configuration file and check whether your previous customizations are still present

Expected Results

  1. The system should be upgraded to Fedora 42 version without error
  2. The bootloader configuration changes should be present in the upgraded system
  3. The system should boot into the updated Fedora without error
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Anaconda_Upgrade_Update_Bootloader&oldid=262889"