Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

After installing leapp on RHEL7, it creates packages that cannot be removed with yum in RHEL8

----%<----
[root@undercloud-0 openstack-tripleo-heat-templates]# yum remove leapp-deps-el8.noarch leapp-repository-deps-el8.noarch
Error:
 Problem 1: package leapp-upgrade-el7toel8-0.14.0-100.202109241452Z.1332835.master.el7_9.noarch requires leapp-repository-dependencies = 6, but none of the providers can be installed
  - conflicting requests
  - problem with installed package leapp-upgrade-el7toel8-0.14.0-100.202109241452Z.1332835.master.el7_9.noarch
 Problem 2: package python2-leapp-0.12.1-100.202109011254Z.8d17bcb.master.el7_9.noarch requires leapp-framework-dependencies = 3, but none of the providers can be installed
  - conflicting requests
  - problem with installed package python2-leapp-0.12.1-100.202109011254Z.8d17bcb.master.el7_9.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
----%<----

It means that other left over from RHEL7 as python2 packages cannot be removed as well

This issue is caused by latest packaging refactoring https://github.com/oamg/leapp-repository/commit/df8c97583b69418e1f7d6a7897b654803a40f090#

It's expected behaviour after we do the next release (we will document it on several places that people will be required to do one additional manual step after the upgrade).

Read this commit msg for an explanation why we had to do this change: https://github.com/oamg/leapp-repository/commit/abe38e8a75d8188928274763c7abca4c62410449

In short, people will be required to update the /etc/dnf/dnf.conf file to drop *leapp* (including snactor) rpms from the exclude line. From the CLI you could use cmd like this one (dropping ALL packages from the exclude line, even additional possible pkgs set by user):
        # dnf config-manager --save --setopt exclude=''