From Fedora Project Wiki

No edit summary
(Adjust phrasing of low disk dialog ... it should not prompt user)
Line 2: Line 2:
|description=This case tests upgrading a Fedora system from the previous stable release ({{FedoraVersion|long|previous}}) to the development release (Rawhide/{{FedoraVersion|long|next}}) using [[PreUpgrade]].
|description=This case tests upgrading a Fedora system from the previous stable release ({{FedoraVersion|long|previous}}) to the development release (Rawhide/{{FedoraVersion|long|next}}) using [[PreUpgrade]].
|actions=
|actions=
# Perform an installation of the previous stable release (e.g. {{FedoraVersion|long|previous}}) with default partitioning (no less than 200MB for <code>/boot</code>). Ensure there are only '''1''' kernel installed on the system.
# Perform an installation of the previous stable release (e.g. {{FedoraVersion|long|previous}}) with default partitioning (no less than 200MB for {{filename|/boot}}). Ensure there are only '''1''' kernel installed on the system.
# Install the newest available version of {{package|preupgrade}}.
# Install the newest available version of {{package|preupgrade}}.
# Run <code>preupgrade</code> from a command prompt or the ''Run Application'' dialog. Provide the requested password for root authorization.
# Run {{command|preupgrade}} from a command prompt or the ''Run Application'' dialog. Provide the requested password for root authorization.
# On the "Choose desired release" screen, enable "unstable test releases".
# On the "Choose desired release" screen, enable "unstable test releases".
# Choose ''Rawhide'' from the list of available upgrade targets.
# Choose ''Rawhide'' from the list of available upgrade targets, then click ''Apply''.
# Click ''Apply''.
# '''NOTE''' - If preupgrade presents a warning dialog noting that additional disk space in {{filename|/boot}} is required to complete the upgrade process, it would be considered a test result of '''FAIL'''. See [http://fedoraproject.org/wiki/How_to_use_PreUpgrade#Troubleshooting methods to free more space in /boot], then click ''Check again''  
# When the process completes, click ''Reboot''.
# When the process completes, click ''Reboot''.
# The system should reboot, perform the upgrade, and reboot into the new system automatically.
# The system should reboot, perform the upgrade, and reboot into the new system automatically.
Line 15: Line 13:
# The preupgrade utility will run to completion, without error.
# The preupgrade utility will run to completion, without error.
# The upgrade should complete and reboot without user assistance.
# The upgrade should complete and reboot without user assistance.
# The user is '''not''' prompted to address low disk space in /boot
# The system should be upgraded to new version without error.
# The system should be upgraded to new version without error.
# The opened terminal, file browser, or other system applications should display and work correctly.
# The opened terminal, file browser, or other system applications should display and work correctly.
}}
}}
[[Category:Upgrade_system]]
[[Category:Upgrade_system]]

Revision as of 15:48, 25 November 2009

Description

This case tests upgrading a Fedora system from the previous stable release (Fedora 40) to the development release (Rawhide/Fedora 42) using PreUpgrade.


How to test

  1. Perform an installation of the previous stable release (e.g. Fedora 40) with default partitioning (no less than 200MB for /boot). Ensure there are only 1 kernel installed on the system.
  2. Install the newest available version of preupgrade.
  3. Run preupgrade from a command prompt or the Run Application dialog. Provide the requested password for root authorization.
  4. On the "Choose desired release" screen, enable "unstable test releases".
  5. Choose Rawhide from the list of available upgrade targets, then click Apply.
  6. When the process completes, click Reboot.
  7. The system should reboot, perform the upgrade, and reboot into the new system automatically.
  8. Log in to upgraded system, open a terminal, file browser, or other system applications.

Expected Results

  1. The preupgrade utility will run to completion, without error.
  2. The upgrade should complete and reboot without user assistance.
  3. The user is not prompted to address low disk space in /boot
  4. The system should be upgraded to new version without error.
  5. The opened terminal, file browser, or other system applications should display and work correctly.