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 801492 - Modify kabi-yum-plugins to abort kernel upgrades on kABI concern
Summary: Modify kabi-yum-plugins to abort kernel upgrades on kABI concern
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kabi-yum-plugins
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Oros
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1296180 1394638 1404314
TreeView+ depends on / blocked
 
Reported: 2012-03-08 16:25 UTC by Jon Masters
Modified: 2016-12-14 03:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-10 10:25:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jon Masters 2012-03-08 16:25:29 UTC 
Description of problem:

If a kernel upgrade affects kABI used by a driver update in a negative fashion, optionally (default to on?) abort the upgrade of the kernel and allow resolution of the problem.
Comment 2 Jon Masters 2013-03-25 13:40:48 UTC 
Clarification: Cover the case of two kernels together providing the total kABI needed by a module but neither individually satisfying the dependencies required of the module. The module (silently) won't be used today, but the install won't fail in an obvious fashion, and this could be a serious problem.
Comment 3 Ludek Smid 2014-06-26 10:42:43 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Comment 4 Ludek Smid 2014-06-26 11:14:17 UTC 
The comment above is incorrect. The correct version is bellow.
I'm sorry for any inconvenience.
---------------------------------------------------------------

This request was NOT resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you need
to escalate this bug.
Comment 5 Stanislav Kozina 2016-11-10 10:25:22 UTC 
Currently, all the Driver Update rpm packages specifically depends on the symbol versions they needed which are provided by the kernel.
The kernel update is still possible (because multiple kernels can be installed at the same time), by the weak-updates script takes care that the incompatible modules are not linked to the kernel modules weak-updates directory.

Very often we need to maintain this situation when a RHEL-7.2 kernel + DUP is installed alongside a RHEL-7.3 GA kernel, which contains the required driver code but might be incompatible with the old DUP.

Thus closing this bug.
Note You need to log in before you can comment on or make changes to this bug.