ERROR - Failed: installing leapp

[pschmid0]

Describe the bug
When running the ./centos2alma, early in the preparation phase, I get:
2024-08-08 16:08:03,930 - INFO - python2-leapp = 0.14.0-1.el7
2024-08-08 16:08:03,930 - INFO - Installing: python2-leapp-0.16.0-2.el7.noarch (elevate)
2024-08-08 16:08:03,930 - INFO - python2-leapp = 0.16.0-2.el7
2024-08-08 16:08:03,930 - INFO - You could try using --skip-broken to work around the problem
2024-08-08 16:08:04,465 - INFO - You could try running: rpm -Va --nofiles --nodigest
2024-08-08 16:08:04,527 - ERROR - Command ['/usr/bin/yum', 'install', '-y', 'leapp-0.14.0-1.el7', 'python2-leapp-0.14.0-1.el7', 'leapp-data-almalinux-0.1-6.el7'] failed with return code 1
2024-08-08 16:08:04,527 - ERROR - Failed: installing leapp. The reason: Command '['/usr/bin/yum', 'install', '-y', 'leapp-0.14.0-1.el7', 'python2-leapp-0.14.0-1.el7', 'leapp-data-almalinux-0.1-6.el7']' returned non-zero exit status 1.

Feedback archive
Please attach a feedback archive to the bug report.
You could create it by calling centos2alma --prepare-feedback.
The archive will help us investigate the problem better and faster.
centos2alma_feedback.zip

[SandakovMM]

It seems we are using new packages from the elevate repositories that are not compatible with leapp 0.14, which we have pinned. I will fix this and recreate the latest release wit the fix.

[pschmid0]

Thanks for looking into this quickly! I really appreciate you working on this. I was wondering if you had an idea of when you will have this fix released so I can schedule a maintenance time for our server to convert to Alma. If not soon, is there a workaround?

[SandakovMM]

Unfortunately, the problem seems significant at the moment. If I cannot find a quick workaround, I will need to switch to the latest Leap update, which may take some time. In that case, I expect to finish it by next weekend.

[pschmid0]

Thanks for the update! I appreciate your efforts. The ETA will help us to do planning and notifying our customers of the upcoming maintenance win we will do the upgrade.

[anemr]

It seems we are using new packages from the elevate repositories that are not compatible with leapp 0.14, which we have pinned. I will fix this and recreate the latest release wit the fix.

Is there a way to install the required 'leapp-0.14.0-1.el7', 'python2-leapp-0.14.0-1.el7', 'leapp-data-almalinux-0.1-6.el7'. Using a different repo? I noticed on my first run the repository file was spelled ELevate but it had the same problem. I removed it and was never recreated, then I installed the repository from https://repo.almalinux.org/elevate/el7/elevate.repo

Still with the same issue. Please provide any information or workaround. Thank you!

[SandakovMM]

I updated to the latest Leapp version to resolve the issue (details in #326). Although I encountered several problems with the Immunify extension which was fixed, everything else seems to be working.
Due to the critical nature of the problem, I released v1.4.0 today to ensure we have a functional version.

[pschmid0]

Thanks for putting the work into this! We appreciate it. Unfortunately, I was unable to get release v1.4.0 to work for my machine. I ended up having to reboot the machine after it put the server in emergency mode. The server did come up, but there were some errors on it. One thing that won't let me continue to try to fix things is at the SSH login, it will log me out as soon as I login. So I have no way to run anything from the command line. I will try a few more things to see if I can get any further.

I am going to make sure everything is updated before starting the process. There were a few things that showed up in "Diagnose & Repair" that I will repair before starting. I will let you know if it gets things working.

[pschmid0]

Well, I never did get it to work. It doesn't start apache and every time I log in, I get logged out immediately.

[SandakovMM]

Do you have a console connection to the instance?
The SSH behavior seems unusual; maybe your system is stuck in a reboot loop

[pschmid0]

This is a Google Cloud VM Instance and I am using the Serial Connection provided by Google Cloud. I can't login if I reboot. It goes to emergency mode before the reboot. I can get you the file '/run/initramfs/rdsosreport.txt' if that will help. It has some errors, one with mariadb.

[mash-tec]

I just wanted to provide some feedback on the new version of the script.

Originally, using version 1.3.3 of the script, I received the same error as the OP during the preparation phase after roughly 2 minutes of it running.

After finding this issue and using version 1.4.0 the upgrade worked as expected without much trouble; so the issue was fixed on my end simply by using the updated version.

[nicholsjl]

I'm just chiming in to corroborate @pschmid0 's issue with the conversion not working for Google Cloud instances. I've tried multiple attempts to run v1.4.2 on one of our servers and every time SSH has stopped working after the automatic reboot. I can only connect using a serial console, but it asks for a login even though it didn't prior to running the conversion tool.

[SandakovMM]

or Google Cloud instances

This might be specific to Google Cloud. I will look into it when I have a chance