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.

Bug 1925103

Summary: [RFE] Leapp could give some clues to explain why a 3rd party package is removed
Product: Red Hat Enterprise Linux 7 Reporter: Christophe Besson <cbesson>
Component: leapp-repositoryAssignee: Leapp Notifications Bot <leapp-notifications-bot>
Status: CLOSED MIGRATED QA Contact: upgrades-and-conversions
Severity: low Docs Contact:
Priority: low    
Version: 7.9CC: amepatil, dhjoshi, fkrska, jcastran, peter.vreman, podvody, pstodulk, rmetrich
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-12 11:09:20 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1818077, 1818088    

Description Christophe Besson 2021-02-04 12:24:03 UTC
Description of problem:
Leapp indicates a 3rd party package will be removed without much details.
Looking into the dependency of the package(s) in question, it appears it requires `groovy`, a package which has been removed in RHEL 8.

Improving the warning could help / ease the user experience, as this kind of 3rd party can be the most important thing installed on the machine.

Version-Release number of selected component (if applicable):
leapp-repository-0.12.0-2.el7_9.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a fake package with a dependency which is removed during the DNF transaction
2. Run a leapp upgrade

Actual results:
"The following packages have not been signed by Red Hat and may be removed during the upgrade process in case Red Hat-signed packages to be removed during the upgrade depend on them"

Expected results:
The package %s has not been signed by Red Hat and may be removed during the upgrade process, due to its dependency to %s.

Additional info:
Just tried a basic and incomplete script (without recursion):
~~~
import rpm, json

msg = "The package %s has not been signed by Red Hat and may be removed during the upgrade process, due to its dependency to %s"

third_party = []
ts = rpm.TransactionSet()
data = ts.dbMatch()
for pkg in data:
    if pkg['vendor'] == 'Red Hat, Inc.' or 'gpg-pubkey' in pkg['name']:
        continue
    deps = []
    for dep in pkg[rpm.RPMTAG_REQUIRENAME]:
        if '/' in dep or '(' in dep:
            continue
        deps.append(dep)
    third_party.append({"name": pkg['name'], "deps": deps})

with open('/etc/leapp/files/pes-events.json', 'r') as fh:
    pes = json.loads(fh.read())

for pkg in third_party:
    for dep in pkg['deps']:
        for x in pes['packageinfo']:
            if dep == x['in_packageset']['package'][0]['name'] \
              and x['out_packageset'] is None:
                print(msg % (pkg['name'], dep))
                break
~~~

~~~
# rpm -q --requires empty
/bin/bash
bash
groovy
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1

# ./check.py 
The package empty has not been signed by Red Hat and may be removed during the upgrade process, due to its dependency to groovy
~~~

Comment 13 Peter Vreman 2021-07-01 10:05:40 UTC
This also impacts RedHat Signed packages of RHSCL, e.g. git2.27
The libssh2 is removed in RHEL8, but it is used by httpd24-libcurl that is then used by rh-git227-git-core

Comment 25 RHEL Program Management 2023-09-12 11:04:20 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 26 RHEL Program Management 2023-09-12 11:09:20 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.