Rocky 8.7 to 8.9 Upgrade

I am currently trying to upgrade a Rocky 8.7 to 8.9 as version 9.x is not support currently on Azure replication for disaster recovery.

I receive the below error messages when try to run this method to upgrade.

REPO_URL=“Index of /vault/rocky/8.9/BaseOS/x86_64/os/Packages/r/

RELEASE_PKG=“rocky-release-8.9-1.9.el8.noarch.rpm”

REPOS_PKG=“rocky-repos-8.9-1.9.el8.noarch.rpm”

GPG_KEYS_PKG=“rocky-gpg-keys-8.9-1.9.el8.noarch.rpm”

sudo dnf install $REPO_URL/$RELEASE_PKG $REPO_URL/$REPOS_PKG $REPO_URL/$GPG_KEYS_PKG
Rocky Linux 8 - AppStream 3.2 MB/s | 10 MB 00:03
Rocky Linux 8 - BaseOS 3.3 MB/s | 3.9 MB 00:01
Rocky Linux 8 - Extras 34 kB/s | 14 kB 00:00
Extra Packages for Enterprise Linux 8 - x86_64 15 MB/s | 14 MB 00:00
rocky-release-8.9-1.9.el8.noarch.rpm 118 kB/s | 23 kB 00:00
rocky-repos-8.9-1.9.el8.noarch.rpm 97 kB/s | 15 kB 00:00
rocky-gpg-keys-8.9-1.9.el8.noarch.rpm 68 kB/s | 13 kB 00:00
No match for argument: /var/cache/dnf/commandline-a76fe31ae310b0c7/packages/rocky-release-8.9-1.9.el8.noarch.rpm
No match for argument: /var/cache/dnf/commandline-a76fe31ae310b0c7/packages/rocky-repos-8.9-1.9.el8.noarch.rpm
No match for argument: /var/cache/dnf/commandline-a76fe31ae310b0c7/packages/rocky-gpg-keys-8.9-1.9.el8.noarch.rpm

The files exist on the site but still have this issue.

I have also cleared cache with dnf and no luck.

Please assist.

Thanks

Where did you get all these instructions from? it should work to simply do dnf update and the resulting update should bring you up to the current Rocky Linux 8.10.

First, Rocky 8 and Rocky 9 are two distinct distros, just like Rocky 8 and Debian are two distinct distros (although Rocky 9 is less dissimilar than Debian).

Rocky 8.7 was Rocky 8 until Rocky 8.8 was released. One was supposed to run dnf up when Rocky 8.8 was released.
Rocky 8.8 was Rocky 8 until Rocky 8.9 was released. …
Rocky 8.9 was Rocky 8 until Rocky 8.10 was released. …
There will be no Rocky 8.11; from now on Rocky 8 will be based on RHEL 8.10 content to 2029.

Rocky does not support past updates. If Azure does not support current Rocky 8, then that is an issue, not the “how to install unsupported packages”.

Looks like Azure support 9.1

How can I get from 8.7 to 9.1 cleanly now?

Like I said, the Rocky 9 is a separate distro. You install it and then transfer confing and user data.

Sometimes I wish RedHat would support version updates. I understand why they don’t, but it does mean a lot of work every 8 years or so… I’m now in the middle of replacing my CentOS7 instances with Rocky 9. It’s hard work. But that’ll keep me going for another 8 years :slight_smile:

Elevate (offered by Alma Linux) can do upgrades between major versions and does support Rocky Linux as a target. There is a non-zero chance that things will go horribly wrong, though and such installations may not be supported by Rocky Linux.

The official position of Rocky Linux is that major version upgrades are not supported and you should do a clean install of the new version.

I’ve tested elevate before on a clean C7 install, doing an C8 upgrade. It… mostly worked. Enough to let me clean up and successfully run the migrate2rocky process :slight_smile:

I believe elevate now supports C7 to Rocky 8 upgrades directly, and Rocky 8 to Rocky 9. It might support C7 direct to Rocky 9 but not sure.

Red Hat does have a tool (leapp). They have a list of setups where it will certainly fail. The Elevate does use the leapp too. (Elevate has non-RHEL data to allow use on non-RHEL distros.)

I prefer to think such operation as in-place conversion to different distro, rather than “upgrade” or “migration”. That, IMHO, makes it more clear what one does attempt.


Yes, there is work. Since I started using configuration management system (Ansible), the install, config, and maintenance got much easier. The transfer of user data is naturally its own hurdle. I have the luxury of network storage that systems mount the “user volumes” from.

You don’t need network storage to do that. You can put your user data on a separate partition and then just mount that partition into the new install without formatting it.