-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
centos stream 9 to rocky 9 migration failure with cannot install the best update candidate for package kernel-devel-matched-5.14.0-474.el9.x86_64 #217
Comments
Can you show your full migrate2rocky.log file please? |
Sure, here it is. |
Do you have kernel* excluded? This appears to be the root of the problem. Other items of note from the log: centos-stream-release seems to be mis-detected as centos-release-automotive. Ultimately this does not appear to be causing any issues but it's something to look into and fix. distro-sync appears to complete and only then errors out. This can be problematic. migrate2rocky9 is looking for a package that matches fwupdate*. This is a relic from migrate2rocky and doesn't appear to be causing any harm, but that should be removed because there are no fwupdate* packages in EL9. |
I do not believe so. I should mention that for the two systems that have failed, they both are using openzfs. I did have 1 openzfs system succeed though. I have completed about 15 systems so far, so only two failures isn't too bad :) I have got a couple of ZFS hosts yet to go, so I'll see if I can increase the debugging on the failing |
I tried another ZFS CS9 box now and got the same failure. I instrumented the |
This seems like a problem to me, running from the host broken with the last comment
So there's no 5.14.0-427.24.1 there, but only 5.14.0-427.22.1 ??? but on a host I manually repaired
|
Sorry to microblog here, so I run
|
So ZFS may be a red herring, the next system (sans ZFS) I tried worked without issue and got kernel |
FWIW, I am migrating my various centos stream 9 hosts to rocky 9 and have hit this error twice today
The text was updated successfully, but these errors were encountered: