Leapp upgrade with 3.11/4.13 fails

Thanks. That patch did the trick. It now ran through.

I had some issues with subscription-manager. I have registered the main server with itself for content which seems to confuse leapp because it thinks it’s registered with redhat. I have played around with various options including --no-rhsm but eventually I have removed subscription-manager before the leapp run.

I also did an dnf autoremove to get rid of the python38 and python39 packages which caused conflicts. As foreman-installer is running after the reboot I was hoping it doesn’t break anything and so far I didn’t find anything.

When it booted up again, it installed the subscription-manager rpm again which reenabled the el8 repos via foreman. I suppose I should have taken care of the before the upgrade.

Now, i have the kdump.service unit in failed status: kdump: No memory reserved for crash kernel.

And dnf always complains about warning: Signature not supported. Hash algorithm SHA1 not available. but doesn’t tell me which signature it is…

But foreman so far seems to be running without complaints.

I’ll revert the vm back to its original state and do another leapp run next week, when I have more time to test the upgraded vm…