Hide Forgot
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.
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.
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.
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.
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.