lvm2-cluster RPM should be considered as an inhibitor for the migration

[esvmicrosoft]

leapp-logs.tar.gz
Actual behavior
I had a centos7 machine where we attemtped to migrate to AlmaLinux 8, everything went well according to the documentation until it came the moment to reboot, then the machine failed to complete the migration and it was unable to boot anymore because it failed to upgrade the lvm2-cluster rpm.

I understand the documentation states ELevate does not support HA clusters but it would be nice if the migration process were halted before rebooting.

To Reproduce
Steps to reproduce the behavior

Get a regular CentOS 7 machine and install the lvm2-cluster RPM, follow the standard process for the migration to AlmaLinux8 and see it fall in flames.

     yum update -y 
     yum install -y lvm2-cluster
     reboot
     sudo yum install -y http://repo.almalinux.org/elevate/elevate-release-latest-el$(rpm --eval %rhel).noarch.rpm
     sudo yum install -y leapp-upgrade leapp-data-almalinux
     sudo leapp preupgrade
     sudo leapp answer --section remove_pam_pkcs11_module_check.confirm=True
     sudo leapp preupgrade
===================================

Total size: 850 M
Total download size: 739 M
Downloading Packages:
Check completed.
====> * report_set_target_release
        Reports information related to the release set in the subscription-manager after the upgrade.
====> * local_repos_inhibit
        Inhibits the upgrade if local repositories were found.
====> * tmp_actor_to_satisfy_sanity_checks
        The actor does NOTHING but satisfy static sanity checks
====> * check_initramfs_tasks
        Inhibit the upgrade if conflicting "initramfs" tasks are detected
==> Processing phase `Reports`
====> * verify_check_results
        Check all dialogs and notify that user needs to make some choices.
====> * verify_check_results
        Check all generated results messages and notify user about them.

Debug output written to /var/log/leapp/leapp-preupgrade.log

============================================================
                           REPORT                           
============================================================

A report has been generated at /var/log/leapp/leapp-report.json
A report has been generated at /var/log/leapp/leapp-report.txt

============================================================
                       END OF REPORT                        
============================================================

Answerfile has been generated at /var/log/leapp/answerfile

Expected behavior
A report in the pre-upgrade process stating the lvm2-cluster rpm can not be installed during the migration process.

System information (please complete the following information):

• cat /etc/system-release

  CentOS Linux release 7.9.2009 (Core)

• Linux centos7ii 3.10.0-1160.118.1.el7.x86_64 #1 SMP Wed Apr 24 16:01:50 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

• [root@centos7ii ~]# rpm -qa| grep leapp leapp-deps-0.14.0-1.el7.noarch leapp-data-almalinux-0.2-5.el7.noarch leapp-upgrade-el7toel8-deps-0.16.0-6.el7.elevate.20.noarch python2-leapp-0.14.0-1.el7.noarch leapp-0.14.0-1.el7.noarch leapp-upgrade-el7toel8-0.16.0-6.el7.elevate.20.noarch
  console_log.txt
  leapp-logs.tar.gz

# rpm -qa "leapp*"
leapp-0.4.0-1.201812151505Z.87a7b74.master.el7_5.noarch
leapp-repository-data-0.4.0-1.201812131256Z.f25d14e.master.el7_5.noarch
leapp-repository-0.4.0-1.201812131256Z.f25d14e.master.el7_5.noarch

Attach (or provide link to) log files if applicable (optional - may contain confidential information):

• All files in /var/log/leapp
• /var/lib/leapp/leapp.db
• journalctl
• If you want, you can optionally send anything else would you like to provide (e.g. storage info)

For your convenience you can pack all logs with this command:

# tar -czf leapp-logs.tar.gz /var/log/leapp /var/lib/leapp/leapp.db

Then you may attach only the leapp-logs.tar.gz file.

---

Additional context
Add any other context about the problem here.

[esvmicrosoft]

console_log.txt
leapp-logs.tar.gz