Upgrading Fedora 26 to Fedora 27

Fedora 27 was just officially released. You’ll likely want to upgrade your system to the latest version of Fedora. Fedora offers a command-line method for upgrading Fedora 26 to Fedora 27. The Fedora 27 Workstation also has a graphical upgrade method.

Upgrading Fedora 26 Workstation to Fedora 27

Soon after release time, a notification appears to tell you an upgrade is available. You can click the notification to launch the GNOME Software app. Or you can choose Software from GNOME Shell.

Choose the Updates tab in GNOME Software and you should see a window like this:

If you don’t see anything on this screen, try using the reload tool at the top left. It may take some time after release for all systems to be able to see an upgrade available.

Choose Download to fetch the upgrade packages. You can continue working until you reach a stopping point, and the download is complete. Then use GNOME Software to restart your system and apply the upgrade. Upgrading takes time, so you may want to grab a coffee and come back to the system later.

Using the command line

If you’ve upgraded from past Fedora releases, you are likely familiar with the dnf upgrade plugin. This method is the recommended and supported way to upgrade from Fedora 26 to Fedora 27. Using this plugin will make your upgrade to Fedora 27 simple and easy.

1. Update software and back up your system

Before you do anything, you will want to make sure you have the latest software for Fedora 26 before beginning the upgrade process. To update your software, use GNOME Software or enter the following command in a terminal.

sudo dnf upgrade --refresh

Additionally, make sure you back up your system before proceeding. For help with taking a backup, see the backup series on the Fedora Magazine.

2. Install the DNF plugin

Next, open a terminal and type the following command to install the plugin:

sudo dnf install dnf-plugin-system-upgrade

3. Start the update with DNF

Now that your system is up-to-date, backed up, and you have the DNF plugin installed, you can begin the upgrade by using the following command in a terminal:

sudo dnf system-upgrade download --releasever=27

This command will begin downloading all of the upgrades for your machine locally to prepare for the upgrade. If you have issues when upgrading because of packages without updates, broken dependencies, or retired packages, add the ‐‐allowerasing flag when typing the above command. This will allow DNF to remove packages that may be blocking your system upgrade.

4. Reboot and upgrade

Once the previous command finishes downloading all of the upgrades, your system will be ready for rebooting. To boot your system into the upgrade process, type the following command in a terminal:

sudo dnf system-upgrade reboot

Your system will restart after this. Many releases ago, the fedup tool would create a new option on the kernel selection / boot screen. With the dnf-plugin-system-upgrade package, your system reboots into the current kernel installed for Fedora 26; this is normal. Shortly after the kernel selection screen, your system begins the upgrade process.

Now might be a good time for a coffee break! Once it finishes, your system will restart and you’ll be able to log in to your newly upgraded Fedora 27 system.

Upgrading Fedora: Upgrade complete!

Upgrading the Fedora Atomic Host

Fedora contributor and Atomic engineer Dusty Mabe has written a complete set of upgrade instructions at the Project Atomic website. Keep in mind that although the Fedora 26 Atomic Host continues to be updated, it is no longer regularly tested or formally released. Because the Atomic Host makes upgrades painless and low-risk (thanks to rollback), all Atomic Host users are recommended to upgrade to Fedora 27.

The short version of the upgrade process follows. These instructions assume you have sufficient space to rebase the new ostree. First, add the remote for the Fedora 27 Atomic Host:

sudo ostree remote add --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-primary fedora-atomic-27 https://kojipkgs.fedoraproject.org/atomic/27

Now upgrade:

sudo rpm-ostree rebase fedora-atomic-27:fedora/27/x86_64/atomic-host

Once you reboot, check the status of your ostree:

rpm-ostree status

You should see your Fedora 27 Atomic Host deployed.

Resolving upgrade problems

On occasion, there may be unexpected issues when you upgrade your system. If you experience any issues, please visit the DNF system upgrade wiki page for more information on troubleshooting in the event of a problem.

If you are having issues upgrading and have third-party repositories installed on your system, you may need to disable these repositories while you are upgrading. For support with repositories not provided by Fedora, please contact the providers of the repositories.

Fedora Project community


  1. Neil Darlow

    I just did the Software Application method of updating from fedora 26 to 27.

    This was on a Toshiba Satellite laptop with Optimus graphics and I had the Rpmfusion-free and Bumblebee and Bumblebee-nonfree repositories enabled.

    The upgrade was performed without any problems whatsoever so it appears the maintainers of the third-party repositories involved were prepared for the fedora 27 release.

    I am now busily exploring the new Firefox 27 and locating replacement addons for the ones I used to use which are now no longer available.

    Good job fedora team on what promises to be another excellent release.

    • Did you get fedora 27 wallpapers? for some reason I did not get them after grnome update.

      • Neil Darlow

        I installed the f27-backgrounds-extras-base and f27-backgrounds-extras-gnome packages afterwards. I am not sure that I have a full set and the timed backgrounds do not appear to work fully.

    • Andre Brait

      If you don’t mind me asking, are you using your NVIDIA card with the official NVIDIA drivers? If so, how are you using them? (Rendering the desktop the whole time or something like primus/bumblebee?)

      I’m asking because up to 26 I couldn’t get it to work with my laptop properly. I could install the drivers but black screen were all I would get after that. Bumblebee worked fine but I had to install from a separate repository that conflicted with negativo17’s.

      • Neil Darlow

        I use the NVIDIA drivers from the bumblebee-nonfree repository and run specific applications with optirun or primusrun.

  2. Matías de la Fuente

    Successful update, everything is working great! \m/

  3. Hoa Le

    At Step # 3, the additional command flag “allowerasing” actually should have another hyphen, otherwise the terminal shows error. Somehow in your article I saw only one long hyphen instead of 2 short hyphens.

    • @Hoa: Thanks, this has been fixed. Unfortunately it was correct in the article text but WordPress automatically changes two hyphens to an em-dash, resulting in an erroneous option.

  4. Greg

    What a boring update! Fast and uneventful. Just as it should be. 😉

    • Chris

      I know. Don’t you miss the old days when sometimes after an upgrade the kernel or filesystem would break and you would get to spend a nervous couple of hours working in the rescue shell trying to avoid having to do a full install, losing all your existing configuration files in the process? Ah, the good old days.

      • Kiran Mathews

        No Chirs…its not….It just happened to me 🙂 and on my birthday! what a lovely gift!!

  5. Angerson Ricardo Lasso Rojas

    Upgrade complete, so easy and everything work perfectly.

  6. Suhas

    Can I upgrade directly from Fedora 23?

    • @Suhas: Not recommended. Your best bet is to upgrade one release at a time.

    • Aymeric

      I’m updating my fedora 23 to fedora 27, one release at a time and for now it’s ok. I’m now on fedora 26, upgrating to fedora 27, last step :).

  7. Avi Wollman

    What is the typical amount of disk space required in order to perform the upgrade on Workstation?

    • @Avi: It’s an individual requirement based on the packages you have installed. If there are unused packages you can remove, that’s one solution.

  8. Noah

    Due to being neurotic I did a fresh install instead of an upgrade from 26 but regardless it is running smoothly. Great work again!

  9. Dutchbird

    Made it.
    This is the most convienient way to upgrade.
    Only that stupid kde wallet has te be disabled.

  10. Tõnu

    Error Summary

    Disk Requirements:
    At least 491MB more space needed on the / filesystem.

    Help please?

    • @Tõnu, see reply to Avi earlier. You can try to clear out unused packages, look for other things you can trim (like system logs — try

      sudo journalctl --vacuum-size 100M

      ), or if you’re using LVM, add some space to /.

  11. Bogdan

    Hello all,
    Why did Filezilla stop working after updating to fedora 27? ;((
    I’m using this ftp client very often and this situation is very uncomfortable for me.
    Does anyone know a solution to this problem?



  12. Hi,
    I used command line, but on the last step I get ‘your system is not ready to upgrade’. Any advice?

    • @Tcharl: You probably have an package that is not GPG signed, or one of your package repositories is not ready with upgraded packages. See if you can remove the unsigned package and then upgrade, or you may have to wait for the repository to be ready, and then upgrade.

    • Daniel Nicolai

      I got the same message. Google/duckduckgo the error messages that you get after the “dnf system-upgrade download” command. In my case I had to manually disable 3rd-party repositories and subsequesntly I still had to remove (dnf remove) the libbsd-devel package (if you have it installed then remove it). This solved the problem

    • I tried to disable gpg, also all third party repo

      • In fact, the machine was already updated: putting a screen on the server brought me the first install step (choosing language, connecting to sass providers, …).

        Sorry for the inconvenience Fedora guys, your distro Rocks (and runs on my PC for about 10 years ;-)).

  13. Brian Murray

    Who has upgraded via the dnf method? Can’t find the upgrade option on the software application.

    • @Brian: The upgrade option appears in the “Updates” tab of the GNOME Software app, as shown in the screenshot. But I’ve upgraded both ways and it was a complete snoozefest — in other words, boring and worked perfectly. 😉

  14. Daniel Nicolai

    After ‘gnome-software’ downloaded about 4.8GB of packages it tells me it is “unable to upgrade to Fedora”. However it does not clean the cache so that my disk drive is full and I have no space left to upgrade with DNF. I checked pkcon how to clean the cache but I could not find the right information. Also during the download of the packages ‘gnome software’ was unresponsive and showed no progress status. Please consider to update via the dnf method. I kindly ask fedora magazine to recommend the dnf method.

    • @Daniel: Try

      journalctl --unit packagekit.service

      to read back through the logs for the error that happened. Usually it means there is a broken package in a non-Fedora repository, an unsigned package, or something else in the way. You can simply use


      to remove that package and try again without re-downloading everything. Or at worst, to clear the cache you can remove /var/cache/PackageKit/27/metadata//packages/.rpm — or you could try moving those packages to the DNF cache to see if it will respect them. I’ve upgraded with both methods and it’s worked fine.

      • Daniel Nicolai

        @Paul: Thanks for your reply. Somehow I only see it now. But I already updated via the dnf method. I hope your information could be added somewhere in the documentation. At least I know about this method now…

      • Daniel Nicolai

        Hi Paul! I tried again with packagekit while upgrading my mother’s laptop. Again it failed, so I tried your method. The journalctl showed two repo’s that failed to upgrade. I disbled the repo’s and removed the packages. After restarting the laptop, as the upgrade still failed with journald reporting the same repo’s, I tried again upgrading with packagekit. However it failed again and the journalctl showed no (for me) no useful information. All messages said ‘finished with succes’ except for the last messag which said ‘dec 11 13:01:23 localhost.localdomain PackageKit[1319]: upgrade-system transaction /1950_caecdcaa from uid 1000 finished with failed after 19212ms’. So again I reverted to the dnf method. No complains. Just for your information. Anyway I learned more about journalctl!

  15. Dell Alienware i17 takes the upgrade without any problem… Had to autoerase dell-hardware-addon to get rid of FC25 packages, but after that, all was smooth and uneventful.

    Thanks Fedora Project!

  16. Upgrade worked just fine on my Lenovo T420 – thank you folks for a very smooth upgrade 🙂

  17. Kevin

    Hello, i have tried to Upgrade my Workstation via command line.
    The dnf system-upgrade download –releasever=27 works without any Problem. But if i Run the dnf system-upgrade reboot command it reboots. After selecting the current Kernel in grub it reboots again Into my old Installation. Nothing happens and i’m back on Fedora 26. Did someone has the Same Problem or a solution?

    • Anon

      Same problem

    • sploit

      I have the exact same problem. At the first reboot it prompts “watchdog did not stop” and “kernel not configured for semaphores”. Disabling selinux does not help.

    • GC

      Exactly the same issue with me on one computer. Hangs at “setting hostname” then reboots without starting installation.

    • Rames

      I have the same problem. I Tried to upadte a few times with


      and with GUI, still it always reboots into Fedora 26 without upgrading anything.

    • Andrés Iniesta

      Same problem

  18. B

    So I saw a “new upgrade available” notification, clicked “download”, and when it was finished, clicked “install”. Everything seemed to be working, so I went for tea. When I came back, it was still busy updating. When it was finally finished and restarted, everything looks okay.

    So I type my password to login … and am rejected. I tried typing my password a few more times, tried the on-screen keyboard instead, tried “GNOME classic” instead of “GNOME”, restarted the computer, attempted the latest 26 version instead of 27, all without any effect, I simply can’t log-in since I’ve upgraded to 27 about an hour ago.

    This is highly frustrating and completely mystifies me. I haven’t experienced something like this when I upgraded from 25 to 26 nor with any other update.
    I use my password at least several times a day and haven’t changed it in months, so I don’t understand why it suddenly stops working upon upgrading. Any idea what happened and how it could easily be solved?

    I’m not looking forward to having to wipe the disk clean and do a completely new installation, which will probably take hours tomorrow.

    • Pero

      I have the same problem. I changed to the other virtual console (ctrl + alt +f7 then ctrl+alt+f2), logged with my usual account there and then typed startx.

      Also using login screen I can login only as root.

  19. Matt B

    I updated and failed to startup on the new kernel image. I was dropped into emergency mode. Checked journald and see the culprit:

    Failed to switch root: Specified switch root path ‘/sysroot’ does not seem to be an OS tree. os-release file is missing initrd-switch-root.service: Main Process exited, code=exited, status=1/FAILURE

    Solved the issue by re-initializing the os-release file to the image. I am not sure why the file was missing or how it got corrupted.

    mount -o remount,rw /sysroot
    rm -f /sysroot/etc/os-release
    cp /usr/lib/os-release /sysroot/etc

    • Alan S

      That worked for me Matt B. Thanks much!

    • Doug

      I had this same error and your steps saved me. Thanks!!

    • Hocine

      You saved me man ! New window animations are on fire btw

    • HBach

      Matt B., thanks so much! This totally saved me! I was able to get back up and running, literally, within minutes!

      This occurred prior to the F27 upgrade while still running F26. I couldn’t resolve it so I was able to grab my data using the Fedora live usb media. I reinstalled F27 twice over the past week and each time after a reboot or two, I ran into this issue. I reinstalled F26 and in ~ 24 hours, after a reboot, ran into the exact same bloody issue again.

      I am back up and running, thanks for the instructions Matt B.!

    • Vikas Kataria

      Sir, Thank you so much … you are a gem !

  20. Alberto Perillo

    I try that few times but fails.

    This worked for me:

    dnf upgrade –refresh

    dnf install dnf-plugin-system-upgrade

    dnf upgrade –releasever=27

    dnf system-upgrade reboot

    • Al Pacifico

      @Alberto: I believe you mean “dnf system-upgrade download –refresh –releasever=27” instead of “dnf upgrade –releasever=27″… see my post below about my experience.

  21. slicer

    Upgraded using the GUI Software app – after reboot wanted get rid of all old packages using ‘dnf autoremove’ – fail, UEFI bios was unable to boot…. so beware!

    • MrAsd

      I also had many issues trying to upgrade from F26 to F27. I first noticed nothing obsoletes grub2-efi-modules, then I encountered the annoying ‘dnf system-upgrade reboot does nothing’ bug, finally I discovered that my freshly upgraded box can’t boot in UEFI mode anymore.

      After countless attempts chrooting from a live image, trying to reconfigure grub2, (re)installing grub2-efi-x64-modules and fiddling with efibootmgr, I gave up and made a fresh install of Fedora 27 (something I strongly recommend to anybody).

      That being said, I am kinda disappointed: your mileage may vary but I feel like I can live without the latest Gnome version while I would definitely prefer a reliable chainloading and system-upgrade “ecosystem”.

      • Juan M.

        Yesterday I had the same problem like you: there isn

        t candidate for grub2-efi-modules in f27, and the only way to do the upgrade is append the option --allowerasing to the upgrade command...this break our uefi boot system with grub2.
        The solution for me,  I don

        t want to do a fresh install, has been:

        ‘sudo dnf install grub2-efi-x64-modules.noarch grub2-efi-x64.x86_64 grub2-common’
        ‘sudo grub2-mkconfig -o /boot/grub2/grub.cfg’
        ‘sudo grub2-install /dev/nvme0n1’ (or /dev/sdX, depends on your needs)

        Taken from:

  22. Emily Lerman

    My computer died during the update and now it says ” failed to setup virtual console”

  23. Robert Smart

    I’m booting my old macbook with just integrated graphics using https://bugzilla.redhat.com/show_bug.cgi?id=765954#c62. This requires grub2-efi-modules. So I hit cancel on fedora27 upgrade because it was going to remove that.

  24. Flawless upgrade! Great work guys!

  25. Dutchy

    Same issue as the others here it sounds like.

    Failed to switch root: Specified switch root path ‘/sysroot’ does not seem to be an OS tree. os-release file is missing initrd-switch-root.service: Main Process exited, code=exited, status=1/FAILURE

    However there is now no os-release file on my system at all.

    Have not found a fix yet. Will try making a bunk os-release and fingers crossed thatll do the trick.

    Pretty livid this shit still happens. I have never been able to update smoothly with new fedora versions. Solution has always been start fresh.

    • HBach

      @Dutchy, please see Matt B.’s post above. I ran into the same issue and his steps worked flawlessly.

  26. Andris Pavenis

    Tried to upgrade from freshly updated (all newer packages as recommended) Fedora 26 workstation to Fedora 27.
    Result: EFI boot totally “foobared”:
    – about 200 new Fedora entries
    – EFI BIOS not able to chew it and goes into continuous boot loop
    Fortunately EFI BIOS on HP EliteBook 8570w allows to chose EFI file to boot directly. This way I succeeded to boot freshly upgraded Fedora 27.

    • Yves L'ECUYER

      I just get the same bug, since Fedora 27 is installed on my EliteBook 8740w
      Each time you boot automatically, it goes into continuous boot loop, and a new entry is added in UEFI monitor, visible with efibootmanager.
      So I had to write a script to remove all these unusefull entries , when there is to many.
      And yes, the only way to boot is to choose the EFI boot manager manually, by navigating in the EFI File system:
      any shim.efi, shimx64.efi, grubx64.efi, under EFI/fedora/ is usable to perform that

      But no automatic boot from “System upgrade bay” is usable, while all that runned fine during many years from Fedora 22 to Fedora 26 !!!!!!!!!!
      What have changed with these release 27 ?
      And waht is the purpose of something like f66bdc3dfcc84e2fbd5cd4469e75ffb8/4.13.13-300.fc27.x86_64 empty directory
      appeared after the upgrade to fedora 27

  27. Mike C

    Updated both my PC’s from 26 to 27 Cinnamon spin no issues whatsoever. Love Fedora

  28. Naveen Nagisetti

    wifi stopped working after updating,


    [root@localhost nnagisetti]# akmods
    Checking kmods exist for 4.13.12-300.fc27.x86_64 [ OK ]
    Ignoring wl-kmod as it failed earlier [WARNING]

    Hint: Some kmods were ignored or failed to build or install.
    You can try to rebuild and install them by by calling
    ‘/usr/sbin/akmods –force’ as root.

  29. Al Pacifico

    Note of caution: I used the commands listed in the post by @Alberto Perillo. Unlike past upgrades, which have generally gone perfectly, this failed on my system as well.

    What I noticed was that it seemed to be installing packages after I executed sudo dnf upgrade –releasever=27 , which was not what I expected. When it was done, I was no longer able to run an exterm terminal or restart via the Gnome selection.

    I was able to access my machine via ssh, however.

    The following repositories were enabled:
    Dropbox Dropbox Repository
    *fedora Fedora 26 – x86_64
    fedora-spotify negativo17 – Spotify
    google-chrome google-chrome
    google64 Google – x86_64
    mysql-connectors-community MySQL Connectors Community
    mysql-tools-community MySQL Tools Community
    mysql57-community MySQL 5.7 Community Server
    nodesource Node.js Packages for Fedora Linux 26 – x86_64
    *rpmfusion-free RPM Fusion for Fedora 26 – Free
    *rpmfusion-free-updates RPM Fusion for Fedora 26 – Free – Updates
    *rpmfusion-nonfree RPM Fusion for Fedora 26 – Nonfree
    *rpmfusion-nonfree-updates RPM Fusion for Fedora 26 – Nonfree – Updates
    skype-stable skype (stable)
    slack slack
    *updates Fedora 26 – x86_64 – Updates

    When I try this again, I will use the command sudo dnf system-upgrade download –refresh –releasever=27 (as suggested by https://fedoraproject.org/wiki/DNF_system_upgrade#Resolving_post-upgrade_issues) instead of the sudo dnf upgrade –releasever=27 suggested above. I may disable all of the external repositories as well.

    • Al Pacifico

      Update: Worked perfectly with all repositories enabled using sudo dnf system-upgrade download –refresh –releasever=27

  30. Robert Murphey

    dnf system-upgrade of 6800+ package install was smooth and by the numbers – congrats Fedora team/community on another release! Onward and upward!

  31. Oleg

    Performed Update via Software. had couple of failed download as some I see here had also but in the end the upgrade was good for most parts.

    Only issue is I cannot select the Application when I click on it. Either on the Favorite bar or All application in Gnome, cannot use the left mouse click to open them. I have to do a right click and new window to open it.

    Anyone else having this issue?

  32. Izauddin Mohd Isa

    When doing dnf upgrade –refresh , I got the following error

    Problem: cannot install the best update candidate for package python2-xapps-overrides-1.0.4-2.fc26.x86_64
    – nothing provides python2-gobject-base(x86-64) needed by python2-xapps-overrides-1.0.4-11.fc26.x86_64

    Can this be ignored ? Try to install the python2-xapps-overrides-1.0.4-11.fc26.x86_64 using
    dnf install python2-xapps-overrides-1.0.4-11.fc26.x86_64 aslo got the same error.

  33. Abdo

    Error Summary

    Disk Requirements:
    At least 3MB more space needed on the /boot filesystem.
    Any help ?

  34. hhuang

    My pc upgrades failed when execute ‘dnf system-upgrade reboot’. In file /var/log/dnf.log , there is ‘Error: Failed to synchronize cache for repo ‘updates’ because of the network is not ready when booting. So it’s not a good idea for system to upgrade depends on network when booting isn’t complete, even i use wifi usually . I figure it out by add ”ExecStartPre=/path/to/my.sh” to /usr/lib/systemd/system/dnf-system-upgrade.service.
    And my.sh is:
    /usr/sbin/ifconfig enp0s25 netmask
    /usr/sbin/route add default gw
    /usr/bin/unlink /etc/resolv.conf
    /usr/bin/cp /home/resolv.conf /etc/
    at last ping google.com for ensure network is good

    • Tomas

      I have the exact same issue when upgrading my Fedora 26 to Fedora 27.

      According to your trick, I just added
      To dnf-system-upgrade.service
      And added
      /usr/bin/systemctl restart NetworkManager.service

      to /usr/local/bin/fix-network.sh

      And don’t forget to add execute permisson to this script.

      I don’t know why this off-line upgrade requires system-online, and network is NOT enabled before this upgrade.

      • Thitho007

        Thx Men !

        Had the same problem while trying to upgrade my Fedora 26 to 27…
        Your workaround works like a charm.

      • Ale

        Same issue here. Also surprised that an off-line upgrade requires network, and then doesn’t provide for it.

    • limace42

      The bug report https://bugzilla.redhat.com/show_bug.cgi?id=1492036 apparently helped with this problem, but what really unlocked the situation for me was to delete




      before I tried to upgrade again.

      If you update your Fedora 26 now (which would include package


      ), then clean the directory and file I mentioned above, you should be able to upgrade to Fedora 27.

  35. Erwan Legrand

    The upgrade fails with the following error.

    Error: Transaction check error:
    file /usr/share/man/man3/explicit_bzero.3.gz conflicts between attempted installs of man-pages-4.12-1.fc27.noarch and libbsd-devel-0.8.3-5.fc27.x86_64

  36. Petrus

    Hi, upgrade went smooth BUT after the first update my dual monitor setup is broken. It does not seem to pick up the extra monitor at all.

    Using HDMI and if I run xrandr in only see the main monitor on the laptop:

    Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
    XWAYLAND0 connected 1366×768+0+0 (normal left inverted right x axis y axis) 340mm x 190mm
    1366×768 59.80*+

    I saw that one of the updates was to fix a monitor issue, but mine was working before that, and not after. Anyone else got this?

  37. Rafal

    Fedora 26 to 27 upgrade went succesfull on my Lenovo T410. Thanks

  38. The upgrade went fine but apparently this is still an issue after upgrading:


    Perl libraries do not seem to work anymore.
    The workaround is to

    sudo mv /usr/local/lib64/perl5 /usr/local/lib64/perl5_old

    and reinstall the stuff you need.

  39. Avinesh

    For me, all upgrade steps went fine. but I am not seeing new kernel entry in my grub and I am still booted with f26 kernel, though all other packages has been upgraded to f27.

  40. northerntracey

    OMG I just checked and my version is Fedora 22!! How do I upgrade from this?

    • Bent

      One version after another 22 -> 23 -> 24 -> … -> 27 would be recommended.

  41. Just wanted to say thanks! F26->F27 went smoothly on my w530.

  42. Kanika (a2batic)

    When I ran sudo dnf upgrade –refresh, the packages were updated, but at the end it showed :-
    PyYAML.x86_64 3.12-3.fc26

    Error: Transaction failed

    When I ran it again, it showed:-

    Problem 1: package epel-release-7-11.noarch conflicts with fedora-release provided by fedora-release-26-1.noarch
    – cannot install the best update candidate for package fedora-release-26-1.noarch
    – cannot install the best update candidate for package epel-release-7-10.noarch
    Problem 2: package rubygem-sinatra-1:1.4.8-2.el7.noarch requires rubygem(rack) < 2, but none of the providers can be installed
    – cannot install both rubygem-rack-1:1.6.4-2.el7.noarch and rubygem-rack-1:2.0.1-3.fc26.noarch
    – cannot install the best update candidate for package rubygem-sinatra-1:1.4.7-3.fc26.noarch
    – cannot install the best update candidate for package rubygem-rack-1:2.0.1-3.fc26.noarch

  43. SampsonF

    The dnf system-upgrade failed on my f26.

    It failed to boot, and I need to do a complete installation of f27 fresh.

  44. Carlos

    Hello, I tried upgrade fedora 26 xfce to fedora 27 all packages download successfully but when I use sudo dnf system-upgrade reboot, the machine reboot but upgrade not appear.

    Please help me



  45. Bent

    As a former Ubuntu user for five years (switched to Fedora about six months ago) I have never seen such a seamless and simple update across desktops and servers.

    Dear Fedora team: Thank you!

  46. Sam Chen

    I just upgraded from fedora 26 to 27 today. It took roughly 4 hours. I did it with command line. The upgrade process worked smoothly. The system also works just like it was before. Great job!

    I have to say it is a remote machine that I do not have a monitor attached to it. Everything was done remotely and it works beautifully. Please continue the hard work! Thank you a bunch!

  47. Kiran

    Did anyone updating from F26 to 27 had issues with python packages?

    I’m getting following conflict issues

    file /usr/bin/pydoc3 conflicts between attempted installs of python34-3.4.5-4.el7.x86_64 and python3-3.6.3-2.fc27.x86_64
    file /usr/bin/python3 conflicts between attempted installs of python34-3.4.5-4.el7.x86_64 and python3-3.6.3-2.fc27.x86_64
    file /usr/bin/pyvenv conflicts between attempted installs of python34-3.4.5-4.el7.x86_64 and python3-3.6.3-2.fc27.x86_64
    file /usr/share/man/man1/python3.1.gz conflicts between attempted installs of python34-3.4.5-4.el7.x86_64 and python3-3.6.3-2.fc27.x86_64
    file /usr/lib64/libpython3.so conflicts between attempted installs of python34-libs-3.4.5-4.el7.x86_64 and python3-libs-3.6.3-2.fc27.x86_64

    • @Kiran: You installed EPEL packages on Fedora which are obviously conflicting with the official Fedora packages. You’ll need to remove them to update since this is not a recommended use for EPEL.

  48. chris

    What about fusion repositories ?
    Is there any problems after upgrading are usable ?

    • Yves

      Personnally, when I made an upgrade I start on my current release with:

      dnf udpdate ferdora-release yum

      So You are sure to get the last Fedora key , used to sign the package provided with the last new realease.
      I have made upgrade from F22 to F23, later from F23 to F25 (directly),
      and just last week from F25 to F27, and was done quite without any problem.

      before doing dnf upgrade, I download also the last rpm:
      for example from F25 to F27, I downloaded
      And installed these with

      dnf update pmfusion-free-release-27.noarch.rpm rpmfusion-nonfree-release-27.noarch.rpm

      (from the directory where theses RPM were stored)

      Now I could do:

      dnf system-upgrade download –releasever=27 –alowerasing

      Before executing the download, there is a summary, where you can see some package, not having anymore their corresponding ones:
      very few in fact (in my case less than 10 packages, on about 4000 packages !)

      You can just make a copy and past of this list, ins some log file , if ever you actually need them later: I mean for example some special package, you need for your environment.
      In my own case , each time i do an upgrade i need to recompile by myself
      kmod-dahdi-linux,from source after the upgrade is completed, and the last new kernel is running. Because this is not provided in the standard Fedora repository.

      then the rest of the procedure described there is running fine.

      Some time, when you have installed i686 libs, on your current 64bits Fedora, some new package, do not manages some duplicated files (generally under /usr/share) in the same way than the previous release.
      Then you have conflicting error message, at the end of the DNF test for upgrade.

      You have the to remove this package, from your current old Fedora running release, before relaunching your dnf upgrade command.

      And then all Fedora, Fedora update, RPM fusion free, RPM fusion non free, and upgraded smoothly !!!

  49. bittin

    This guide worked good, just updated was waiting for new Icinga packages so could not update when it was released, but its fixed now

  50. Nicolas


    Thanks for this guide ! I’ve just updated Fedora 26 -> 27, and I have a problem to complete it with the Fedora Atomic Host step.

    When I launch

    sudo ostree remote add –set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-primary fedora-atomic-27 https://kojipkgs.fedoraproject.org/atomic/27

    it gives me an error : Command requires a –repo argument

    I am quite new to Linux, so thank you for your help 🙂 I allready googled, but couldn’t find the problem

    • Hi Nicolas,

      I believe you get that error if you are not running on an Atomic Host system already. Did you start with a Fedora Atomic Host system or a plain Fedora Workstation or Server install? If you aren’t running an Atomic Host system then you don’t need to do these steps! If you are running an Atomic Host system please find me in IRC (dustymabe in #atomic) or send a mail to atomic-devel@projectatomic.io and we’ll debug the problem!


      • Nicolas

        Oh ! Thanks ! I installed Fedora 26 from the Media tool, so you’re probably right, from it I didn’t have an Atomic host. So problem solved 🙂


Comments are Closed

The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat. Fedora Magazine aspires to publish all content under a Creative Commons license but may not be able to do so in all cases. You are responsible for ensuring that you have the necessary permission to reuse any work on this site. The Fedora logo is a trademark of Red Hat, Inc. Terms and Conditions