Package update required migrating from RHEL to Rocky

Rocky Linux Tech Help
1

Hello,

I would like to ask if when a migration is done from RHEL and Rocky via rocky-tools/migrate2rocky/migrate2rocky.sh at main · rocky-linux/rocky-tools · GitHub is it mandatory to do a dnf update.

Would it be possible to avoid this?

Thank you,
E

2

Welcome to the forums.

It’s not recommended to skip a dnf update during a migration. There is an expectation that the system you’re migrating from and our repositories are at the same package version levels to ensure a smooth migration.

Is there a reason why you’d want to skip an update?

3

Hi nazunalika,

Thank you for responding. I understand the need to do a dnf update and the reason you gave makes sense.

I thought of asking this because some of our customers have processes that can slow down when migrating from RHEL to Rocky also has a package update in parallel.

We will proceed in this direction that following the guidelines recommended by the Rocky community.

Thank you for your support.

4

I have a similar but different scenario. My RHEL developer license expired - again, and it’s an annoying waste of time trying to get it renewed. So at the moment I can’t access the RHEL repo.
Can the migrate be done just by using the Rocky8 repo instead?
Is so, how?

5

Unfortunately migrate2rocky does require active repositories in the distro you are migrating from to work properly. I realize just how much of a pain it is, but I would recommend that you renew your devsub one more time in order to perform the migration.

6

Just to add to the answer already given, migrate2rocky not only requires a dnf update prior to migration but performs one itself to make sure (I still recommend doing it yourself, though).