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 2015578

Summary: kernel panic after upgrade from rhel7.9 to 8.5-RC
Product: Red Hat Enterprise Linux 7 Reporter: Michal Macura <mmacura>
Component: leapp-repositoryAssignee: Petr Stodulka <pstodulk>
Status: CLOSED ERRATA QA Contact: Martin KlusoĊˆ <mkluson>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.9CC: bgoncalv, mkluson, mreznik, pstodulk
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: leapp-repository-0.15.0-6.el7_9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-10 09:13:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 7 Petr Stodulka 2021-11-03 14:02:06 UTC
The issue has been fixed by the following PR (applied in downstream as well):
  - https://github.com/oamg/leapp-repository/pull/754

We have realized the problem has not been connected to RHEL 8.5 at all and it's reproducible for upgrades to RHEL 8.4 as well. The problem has been created by incorrect / incomplete list of packages given to DNF for the installation - based on PES data. Not sure whether the mix of RHEL 7 & 8 packages has been present after the upgrade or whether dependencies in "core" packages are incomplete. In any way, we have fixed the issue introduced by the new repomapping mechanism.

The issue itself is reproducible on systems that do not have enabled RHEL 7 Base repository. This usually happens for detached systems (but not only). On such systems we could not find a representative RHEL 7 repository that could give us right "markers" find best candidates for RHEL 8 repositories. To fix the issue, we have implemented fallback mechanism, to use a default "markers" for the search of target repositories.

Reproducer:
- drop / disable all RHEL 7 repositories when all expected RHEL 7 packages are present
- enable a non-RH repository (e.g. leapp COPR repository)
- do the upgrade

Note: the problem can be checked even before the reboot, just checking the  /var/log/leapp/dnf-plugin-data.txt content. In case of the issue, the to_install and to_upgrade lists will be empty. In other cases, the lists will always contain some packages.

Comment 10 errata-xmlrpc 2021-11-10 09:13:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (leapp, leapp-repository, and cockpit-leapp bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4603