Before we get started, I really ought to drop this here:
You have a few other methods to get the upgrade done:
- Toss in a CD or DVD: You can upgrade via the anaconda installer provided on the CD, DVD or netinstall media. My experiences with this method for Fedora (as well as CentOS, Scientific Linux, and Red Hat) haven’t been too positive, but your results may vary.
- Download the newer release’s fedora-release RPM, install it with
yum upgrade: This is the really old way of doing things. Don’t try this (read the next bullet).
yum’s distro-sync functionality: If you can’t go the
preupgraderoute, I’d recommend giving this a try. However, leave plenty of time to fix small glitches after it’s done (and after your first reboot).
Personal anecdote time (Keep scrolling for the meat and potatoes)
I have a dedicated server at Joe’s Datacenter (love those folks) with IPMI and KVM-over-LAN access. The
preupgrade method won’t work for me because my
/boot partition is on a software RAID volume. There’s a rat’s nest of a Bugzilla ticket over on Red Hat’s site about this problem. I’m really only left with a live upgrade using
yum upgrade process
Before even beginning the upgrade, I double-checked that I’d applied all of the available updates for my server. Once that was done, I realized I was one kernel revision behind and I rebooted to ensure I was in the latest Fedora 15 kernel.
A good practice here is to run
package-cleanup --orphans (it’s in the
yum-utils package) to find any packages which don’t exist on any Fedora mirrors. In my case, I had two old kernels and a JungleDisk package. I removed the two old kernels (probably wasn’t necessary) and left JungleDisk alone (it worked fine after the upgrade). If you have any external repositories, such as Livna or RPMForge, you may want to disable those until the upgrade is done. Should the initial upgrade checks bomb out, try adding as few repositories back in as possible to see if it clears up the problem.
Once you make it this far, just follow the instructions available in Fedora’s documentation: Upgrading Fedora using yum. I set SELinux to permissive mode during the upgrade just in case it caused problems.
I’d recommend skipping the
grub2-install portion since your original grub installation will still be present after the upgrade. If your server has EFI (not BIOS), don’t use
grub2 yet. Keep an eye on the previously mentioned documentation page to see if the problems get ironed out between
grub2 and EFI.
Before you reboot, be sure to get a list of your active processes and daemons. After your reboot, some old SysVinit scripts will be converted into Systemd service scripts. They might not start automatically and you might need to enable and/or start some services.
New to Systemd? This will be an extremely handy resource: SysVinit to Systemd Cheatsheet.
I haven’t seen too many issues after cleaning up some daemons that didn’t start properly. There is a problem between
asterisk and SELinux that I haven’t nailed down yet but it’s not a showstopper.
Good luck during your upgrades. Keep in mind that Fedora 15 could be EOL’d as early as May or June 20102 when Fedora 17 is released.