Ask Your Question
1

"nothing to do" when trying to upgrade

asked 2019-02-10 12:51:41 -0500

rockaday gravatar image

updated 2019-02-10 13:16:22 -0500

A few weeks ago I was on Fedora 24. Realizing I was waaaayyy behind and really needed to upgrade, I attempted to upgrade Fedora one major version at a time. Following Fedora Magazine instructions I upgraded to Fedora 25 fine.

I should have stuck with those steps. I don't remember whether I did them one more time to get to 26 first, but at some point I decided to try other instructions I found that I mistakenly thought were more current. I inadvertently wound up on Rawhide.

I managed to get off Rawhide following these steps. But now something seems off, as I don't appear to be able to upgrade to Fedora 27. DNF tells me there's nothing to do, and after I reboot my /etc/fedora-release file hasn't changed.

Here's what I see:

$ cat /etc/fedora-release
Fedora release 26 (Twenty Six)

$ sudo dnf upgrade --refresh
Repository InstallMedia has no mirror or baseurl set.
Last metadata expiration check: 0:00:00 ago on Sun 10 Feb 2019 06:42:17 PM UTC.
Dependencies resolved.
Nothing to do.
Complete!

$ sudo dnf install dnf-plugin-system-upgrade
Repository InstallMedia has no mirror or baseurl set.
Last metadata expiration check: 0:00:26 ago on Sun 10 Feb 2019 06:42:17 PM UTC.
Package python3-dnf-plugin-system-upgrade-2.0.5-1.fc26.noarch is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!

$ sudo dnf system-upgrade download --releasever=27
Repository InstallMedia has no mirror or baseurl set.
Before you continue ensure that your system is fully upgraded by running "dnf --refresh upgrade". Do you want to continue [y/N]: y
Last metadata expiration check: 0:00:00 ago on Sun 10 Feb 2019 06:48:14 PM UTC.
Dependencies resolved.
Nothing to do.
Complete!
Download complete! Use 'dnf system-upgrade reboot' to start the upgrade.
To remove cached metadata and transaction use 'dnf system-upgrade clean'

$ sudo dnf system-upgrade reboot

After it reboots, this is unchanged:

$ cat /etc/fedora-release
Fedora release 26 (Twenty Six)

How can I get my system to a good state so I can continue upgrading, one version at a time, to Fedora 29?

Is there other diagnostic information I should post here? This is a remote, hosted instance of Fedora server (a linode), so I don't see whatever might print at bootup.

Thanks in advance for any help.

edit retag flag offensive close merge delete

Comments

1

Can you post the content of your /etc/yum.repos.d/fedora.conf , I has this because this message " has no mirror or baseurl set." which mean it is not connecting to the repos.

aeperezt gravatar imageaeperezt ( 2019-02-10 14:57:17 -0500 )edit

3 Answers

Sort by ยป oldest newest most voted
1

answered 2019-04-06 15:51:06 -0500

rockaday gravatar image

I finally resolved the issue I posted about above. Thank you to users aeperezt and rdtcustomercare for helping me get past the first hurdle.

Apparently switching to rawhide disabled my fedora and fedora-updates repos. grep enabled /etc/yum.repos.d/*.repo was helpful. I had managed to disable rawhide a while ago, but then I had zero repos enabled, which was blocking my upgrade. I enabled fedora and fedora-updates. Then I tried the upgrade instructions at fedora magazine again.

First I had to remove yum-utils, as it was blocking installation of dnf-utils.

Then it showed over 300MB of upgrades available. Unfortunately the final reboot & install step still failed.

Pouring through journalctl logs, I finally found this about 2,600 lines back after the installation failure:

systemd-journald[374]: Suppressed 1 messages from /system.slice/dnf-system-upgrade.service
  Running scriptlet: filesystem-3.3-3.fc27.x86_64                           1/1
  Running scriptlet: npm-1:6.4.1-1.8.12.0.1.fc27.x86_64                     1/1
  Running scriptlet: nodejs-inherits-2.0.3-2.fc27.noarch                    1/1
  Preparing        :                                                        1/1Transaction couldn't start:
file /usr/lib/node_modules/npm/doc from install of npm-1:6.4.1-1.8.12.0.1.fc27.x86_64 conflicts with file from package nodejs-2:8.2.1-1nodesource.fc24.x86_64
file /usr/lib/node_modules/npm/html from install of npm-1:6.4.1-1.8.12.0.1.fc27.x86_64 conflicts with file from package nodejs-2:8.2.1-1nodesource.fc24.x86_64
file /usr/lib/node_modules/npm/man from install of npm-1:6.4.1-1.8.12.0.1.fc27.x86_64 conflicts with file from package nodejs-2:8.2.1-1nodesource.fc24.x86_64
Error: Could not run transaction.
systemd[1]: dnf-system-upgrade.service: Main process exited, code=exited, status=1/FAILURE

The primary purpose of this linux node was to run a website. The TLS cert had expired because the operating system was too outdated to easily install the script to renew it. The site was down because I was stuck while trying to upgrade from Fedora 24 to 29 (one upgrade at a time -- part of the disruption was also due to the postgresql upgrade that came with the OS upgrades). So in short: an npm error brought down my linux box.

I removed nodejs, I do not use it and did not care to have it installed anyway. The upgrades worked great after that. I still had to deal with migrating my postgres data from 9.5.7 to 10.7.x, but that's another story.

edit flag offensive delete link more
1

answered 2019-02-10 19:04:09 -0500

rockaday gravatar image

Thanks for the assistance. I was able to execute the commands, but something is still a little off, and I'm not sure what you mean by "run it step by step" (run what, how?).

Here's what I see:

$ cat /etc/fedora-release
Fedora release 26 (Twenty Six)

$ sudo dnf list --installed | head -n20
Repository InstallMedia has no mirror or baseurl set.
Installed Packages
GeoIP.x86_64                           1.6.11-1.fc26               @@commandline
GeoIP-GeoLite-data.noarch              2018.04-1.fc26              @@commandline
NetworkManager.x86_64                  1:1.8.2-4.fc26              @@commandline
NetworkManager-libnm.x86_64            1:1.8.2-4.fc26              @@commandline
NetworkManager-ppp.x86_64              1:1.8.2-4.fc26              @@commandline
NetworkManager-team.x86_64             1:1.8.2-4.fc26              @@commandline
PackageKit.x86_64                      1.1.6-2.fc26                @@commandline
PackageKit-glib.x86_64                 1.1.6-2.fc26                @@commandline
aajohan-comfortaa-fonts.noarch         3.001-1.fc26                @@commandline
abrt.x86_64                            2.10.3-4.fc26               @@commandline
abrt-addon-ccpp.x86_64                 2.10.3-4.fc26               @@commandline
abrt-addon-coredump-helper.x86_64      2.10.3-4.fc26               @@commandline
abrt-addon-kerneloops.x86_64           2.10.3-4.fc26               @@commandline
abrt-addon-pstoreoops.x86_64           2.10.3-4.fc26               @@commandline
abrt-addon-python3.x86_64              2.10.3-4.fc26               @@commandline
abrt-addon-vmcore.x86_64               2.10.3-4.fc26               @@commandline
abrt-addon-xorg.x86_64                 2.10.3-4.fc26               @@commandline
abrt-cli.x86_64                        2.10.3-4.fc26               @@commandline
abrt-dbus.x86_64                       2.10.3-4.fc26               @@commandline

$ ls /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-2[6-9]*
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-aarch64@   /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-aarch64@  /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-armhfp@   /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-i386@
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-armhfp@    /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-armhfp@   /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-i386@     /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-ppc64@
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-i386@      /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-i386@     /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-ppc64@    /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-ppc64le@
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-ppc64@     /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-ppc64@    /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-ppc64le@  /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-ppc64le@   /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-ppc64le@  /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-primary   /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-s390x@
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-primary    /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-primary   /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-s390x@    /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-x86_64@
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-s390x@     /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-s390x@    /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-x86_64@
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-secondary  /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-x86_64@   /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-aarch64@
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-x86_64@    /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-aarch64@  /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-armhfp@

$ uname -i
x86_64

$ sudo dnf --allowerasing --releasever=27 --setopt=deltarpm=false distro-sync
Repository InstallMedia has no mirror or baseurl set.
Docker CE Stable - x86_64                                                                                                                                                           38 kB/s |  10 kB     00:00
Last metadata expiration check: 0:00:00 ago on Mon 11 Feb 2019 01:02:19 AM UTC.
Dependencies resolved.
===================================================================================================================================================================================================================
 Package                                            Arch                                        Version                                                Repository                                             Size
===================================================================================================================================================================================================================
Downgrading:
 containerd.io                                      x86_64                                      1.2.0-3.fc27                                           docker-ce-stable                                       18 M
 docker-ce                                          x86_64                                      3:18.09.0-3.fc27                                       docker-ce-stable                                       19 M
 docker-ce-cli                                      x86_64                                      1:18.09.0-3.fc27                                       docker-ce-stable                                       14 M

Transaction Summary
===================================================================================================================================================================================================================
Downgrade  3 Packages

Total download size: 51 M
Is this ok [y/N]: N

I'm still not sure how to get from here to Fedora 27.

Thanks again.

edit flag offensive delete link more

Comments

1

That is very suspiciose as you have f26 packages installed and should be upgrade to f27/f28/f29 in one "step" .

A) could it be, that it is not a native fedora install ? The repo names are strange B) run "grep "enabled=" /etc/yum.repos.d/*" for me pls. This will show us the names and states of your available repositiories.

If you see "fedora" and "updates" with "enabled=0", enable(1) them and try the upgrade again.

A normal untampered fedora installation has only repos with "fedora" in the filename like "fedora-updates.repo" and "fedora-updates-testing.repo". If you find docker, stop ....

rdtcustomercare gravatar imagerdtcustomercare ( 2019-02-11 03:30:12 -0500 )edit
1

like i said, looks like repos are not enabled:

grep enable /etc/yum.repos.d/*

rdtcustomercare gravatar imagerdtcustomercare ( 2019-02-24 10:12:32 -0500 )edit
0

answered 2019-02-10 14:54:22 -0500

updated 2019-02-10 14:56:34 -0500

dnf update does nothing when there a no new packages.

What you need is a distro-upgrade :

1) use "screen" to have a terminal running in case something ( GDM restarts etc) wents wrong

CTRL+F4 will bring you in a text console where you can get back to your upgrade session with "screen -r" ofcourse you could start it there right away, but the resolution may not be the best. I prefer a big terminal, but thats just me. usually it will work without interruptions. You have been warned and instructed ;)

2) upgrade your installation manually :

rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-$(uname -i)

dnf clean all;dnf upgrade; ( you can skip this in your case )

dnf --allowerasing --releasever=26 --setopt=deltarpm=false distro-sync

-> use any higher rev as 26 if you already have ugraded to 26. <-

Note: you can't upgrade to many revision ahead, because you lack the key for it. Solutions: you use 2 rev steps OR you get the keys for the newest fedora version from the webpage.

If you can't find it, run it step by step. This has the advantage of correcting mistakes and makes changes you otherwise would miss ( i.e. the /bin/ to /usr/bin/ fs corrections some fedora releases ago / just an example )

Have fun.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2019-02-10 12:51:03 -0500

Seen: 93 times

Last updated: Apr 06