Created attachment 328467 [details] Proposed patch Description of problem: 5.1.19.6-44 includes a fix for bug #476866 that breaks with kernel prior to 2.6.18-122.el5 which have no module dm-mem-cache dm-region_hash dm-message or dm-raid45. Version-Release number of selected component (if applicable): mkinitrd-5.1.19.6-44 How reproducible: 100% reproducible Steps to Reproduce: 1. install mkinitrd-5.1.19.6-44 2. Run kernel 2.6.18-120.el5 3. mkinitrd initrd-$(uname -r) $(uname -r) Actual results: No module dm-mem-cache found for kernel 2.6.18-120.el5, aborting. Expected results: initrd-2.6.18-120.el5 created Additional info: I think the fix for bug #476866 should have been: if [ "$withdmraid" == "1" ]; then findmodule -dm-mem-cache findmodule -dm-region_hash findmodule -dm-message findmodule -dm-raid45 fi ie use "-" which instructs findmodule not to break if the module is not present.
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.
This is fixed in mkinitrd-5.1.19.6-45 .
*** Bug 488991 has been marked as a duplicate of this bug. ***
On a RHEL5.2 machine I've upgraded mkinitrd to version 5.1.19.6-44 which is the one reported to fail. # rpm -q mkinitrd mkinitrd-5.1.19.6-44 # uname -a Linux dell-pe650-02.rhts.bos.redhat.com 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:12 EDT 2008 i686 i686 i386 GNU/Linux # mkinitrd test-$(uname -r) $(uname -r) No module dm-mem-cache found for kernel 2.6.18-92.el5, aborting. Then upgrade mkinitrd to the latest available version. # rpm -q mkinitrd mkinitrd-5.1.19.6-52 # uname -a Linux dell-pe650-02.rhts.bos.redhat.com 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:12 EDT 2008 i686 i686 i386 GNU/Linux # mkinitrd test-$(uname -r) $(uname -r) cat: /proc/sys/crypto/fips_enabled: No such file or directory /sbin/mkinitrd: line 1171: [: : integer expression expected /sbin/mkinitrd: line 1663: [: : integer expression expected /sbin/mkinitrd: line 1748: [: : integer expression expected # echo $? 0 The initrd image is created but notice the errors. I guess that's another bug. QE will need to re-test this once the errors are fixed. Tested on i386 and ia64 since customer is using ia64 in comment #9.
QE Note: please test after bug #502624 has been verified.
Alexander, this bug can be tested against mkinitrd-5.1.19.6-45 , as I said above in comment #7. It need not block on 502624.
# ls -l /proc/sys/crypto/fips_enabled ls: /proc/sys/crypto/fips_enabled: No such file or directory # rpm -q mkinitrd mkinitrd-5.1.19.6-53 # uname -a Linux athlon5 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:12 EDT 2008 i686 athlon i386 GNU/Linux # mkinitrd test-$(uname -r) $(uname -r) # echo $? 0 # ls -l test-2.6.18-92.el5 -rw------- 1 root root 3118733 May 27 04:09 test-2.6.18-92.el5 initrd image is created and no error for /proc/sys/crypto/fips_enabled. Tested on i386 and ia64 since customer is using ia64 in comment #9. Moving to VERIFIED.
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-1345.html