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.

Created attachment 435266 [details]
script session demonstrating the problem

Description of problem:
When a kmod is installed and an incompatible kernel is to be installed, rpm dependency checking does not cause an error or warning message (rpm -iv or yum install)

An error is only generated if the kernel is updated (rpm -Uv or yum update).


Version-Release number of selected component (if applicable):
module-init-tools 3.9-15.el6


How reproducible:
always


Steps to Reproduce:
1. install RHEL6 beta2 (2.6.32-37.el6)
2. install kmod
3. install new, incompatible kernel (e.g. snapshot8: 2.6.32-52.el6) with rpm -i
  
Actual results:
succeeds

Expected results:
error or warning message.

Additional info:
This may lead to a situation where the customer can't boot the default kernel because of a missing kmod. In RHEL5, the "yum-kmod" plugin with the "installforallkernels" option fulfilled this requirement, but yum-kmod is no longer available.

I am attaching a script session demonstrating what I mean.

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

The RHEL6 kernels prior to GA release of RHEL6.0 may introduce such "incompatibilities" because we do not offer a kABI guarantee until the official release of RHEL6.0. The situation described in this bug should not arise in production, however I am willing to consider adding logic to catch this into the optional yum plugin we have created for RHEL6.0. I have raised this for internal discussion on the matter for 6.0 or 6.1 consideration accordingly.

Jon.

The situation described in this bug should not arise in production. We've discussed the matter internally and because this is unlikely to occur, we've determined that we'd rather use the resources required on other projects.