Description of problem: The following messages are output during kmod installation. [root@dhcp47-139 dup]# rpm -ihv kmod-dup_cert_pass-1.0-0.ia64.rpm Preparing... ########################################### [100%] 1:kmod-dup_cert_pass ########################################### [100%] modinfo: could not open /lib/modules/2.6.18-121.el5/extra/dup_cert_pass: Is a directory FATAL: /lib/modules/2.6.18-121.el5/extra/dup_cert_pass: Is a directory Warning: Module dup_cert_pass from kernel has no modversions, so it cannot be reused for kernel 2.6.18-120.el5 modinfo: could not open /lib/modules/2.6.18-121.el5/extra/dup_cert_pass: Is a directory FATAL: /lib/modules/2.6.18-121.el5/extra/dup_cert_pass: Is a directory Warning: Module dup_cert_pass from kernel has no modversions, so it cannot be reused for kernel 2.6.18-122.el5 Version-Release number of selected component (if applicable): redhat-rpm-config-8.0.45-27.el5 How reproducible: Always. Steps to Reproduce: 1. Install two or more kernels in the system. 2. Install your kmod RPM that was built on 5.3 environment. Actual results: The messages are output. Expected results: No messages are output. Additional info: - Seems the changes to the logic to obtain the paths of modules in kmodtool are the cause of the problem. Old: modules=( \$(rpm -ql kmod-${kmod_name}${dashvariant} | grep '\.ko$') ) New: modules=( \$(find /lib/modules/${verrel}${variant}/extra/${kmod_name}) ) find returns directories as well, making modinfo complain. - Because of above, an installation of kmod that was built on 5.2 environment completes without the messages. (The kmod contains the old logic in itself.)
Created attachment 326321 [details] Proposed patch
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
Rebuild this package with a fix similar to that posted. Thanks!
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0224.html