Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1136030

Summary: Need a new chapter about upgrading Fedora
Product: [Retired] Fedora Documentation Reporter: Petr Bokoc <pbokoc>
Component: install-guideAssignee: Petr Bokoc <pbokoc>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: me, pbokoc, wifienclair, zach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 09:21:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1008749, 1044541    
Bug Blocks:    

Description Petr Bokoc 2014-09-01 13:26:54 UTC
The current upgrade chapter is pretty much completely useless. We need a new one that would cover:
* Automatic upgrades with FedUp, including how to prepare and how to clean up after the update finishes
* Manual upgrade (or reinstall) - manually booting the installer on an existing system and using the normal installation process to overwrite the root filesystem while keeping the rest of the system (/home and any other separate filesystems) intact.

There should be ample documentation on FedUp on the Fedora Wiki.

Comment 1 Petr Bokoc 2014-09-01 13:38:52 UTC
*** Bug 1001049 has been marked as a duplicate of this bug. ***

Comment 2 Pete Travis 2016-03-06 20:35:32 UTC
Update: this is still needed, but in-place distribution upgrades should now be performed with the dnf system-upgrade plugin instead of fedup.

Comment 3 Petr Bokoc 2024-05-21 09:21:52 UTC
The install guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.