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

Bug 901692

Summary:	Conflict in preupgrade instructions
Product:	[Retired] Fedora Documentation	Reporter:	Bob Gustafson <bobgus>
Component:	install-guide	Assignee:	Pete Travis <me>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ruediger Landmann <rlandman+disabled>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	dew, me, 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:	2013-03-25 13:25:37 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:
Bug Blocks:	919665

Description Bob Gustafson 2013-01-18 20:24:18 UTC

Description of problem:
 I am venturing forth on an upgrade from Fedora17 to Fedora18. I have raid1 systems. My first question is whether I should use Preupgrade or FedUp.

The documentation reads:

Upgrade to current release directly
Preupgrade provides an upgrade directly to the latest version of Fedora from the previous two versions. It is not necessary to upgrade to intermediate versions. For example, it is possible to upgrade from Fedora 16 to Fedora 18 directly, but not directly from earlier versions.

Preupgrade deprecated for Fedora 18
Preupgrade does not at present and will not ever work for upgrading to Fedora 18, or any version after that. It was replaced by FedUp.


Version-Release number of selected component (if applicable):

  https://fedoraproject.org/wiki/How_to_use_PreUpgrade?rd=PreUpgrade

How reproducible:

 Every time I read it, I don't understand the same thing.

Steps to Reproduce:
1. load https://fedoraproject.org/wiki/How_to_use_PreUpgrade?rd=PreUpgrade into browser
2. read the 2nd and 3rd paragraphs
3.
  
Actual results:

  Puzzlement

Expected results:

  A clear statement of what to do and what not to do.

Additional info:

Comment 1 Bob Gustafson 2013-01-18 23:32:13 UTC

Ok, things are going good. I used FedUp - with network source. I didn't have to burn any DVDs.

sudo fedup-cli --network 18 --debuglog fedupdebug.log

Then reboot into the installation.

Finished one system, now working on the 2nd.

No glitches so far.

Comment 2 Bob Gustafson 2013-01-19 00:27:18 UTC

After I was up in Fedora 18, I updated grub with the following commands:

Since this is a raid1 and I want to be able to boot no matter which disk fails..

grub2-install /dev/sda
grub2-install /dev/sdb

Then

cd /boot/grub2
cp grub.cfg grub2.cfg.bakup

grub2-mkconfig -o /boot/grub2/grub.cfg

Just for curiosity

diff grub.cfg grub.cfg.bakup

Then redo the install.. (may not be necessary, but why not)

grub2-install /dev/sda
grub2-install /dev/sdb

Then

ln -sf /boot/grub2/grub.cfg /etc/grub2.cfg

==========

I'm still waiting for the 2nd system to update.. fingers crossed.

Comment 3 Bob Gustafson 2013-01-19 01:47:32 UTC

2nd system boots fine and boots after grub reconfig as above.

I wonder whether there is an application that comes around in a few weeks after everything has settled down and deletes all of the Fedora 17 stuff that is not needed. I see a lot of kernels with .f17 endings in the /boot directory. Those may not run well now..

----

Congratulations to the FedUp team. At last - Fedora is out of the grip of Anaconda..

Comment 4 Donald Edward Winslow 2013-02-26 03:20:18 UTC

This bug is about the wiki, not the Docs. In any case, it should be closed, because someone fixed it on the wiki. It makes sense now.

btw, the f17 kernels should have disappeared by now with updates. It's a good idea to look for other obsolete packages to erase.

Comment 5 Pete Travis 2013-03-25 13:25:37 UTC

Hey Bob,

I'm glad you were able to get your system updated - I'm exited about FedUP too. For cleanup after an upgrade, these ( http://fedorasolved.org/Members/fenris02/post_upgrade_cleanup ) instructions are quite rigorous. 

The PreUpgrade wiki page has been tagged to let readers know the versions it applies to, so I'm closing this bug.  You've brought up a couple ideas that we can chalk on our todo list, though. First /boot on RAID1, with grub installed to each member, and adding some post-upgrade instructions to a guide.