Bug 699553 - Output "Modulefile is /etc/modprobe.conf" during kernel update
Summary: Output "Modulefile is /etc/modprobe.conf" during kernel update
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mkinitrd
Version: 5.6
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-25 23:13 UTC by Robert Scheck
Modified: 2018-11-14 12:52 UTC (History)
3 users (show)

Fixed In Version: mkinitrd-5.1.19.6-71
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-23 21:19:22 UTC
Target Upstream Version:


Attachments (Terms of Use)
mkinitrd-5.1.19.6-bz699553-correct-echo-by-vecho.patch (926 bytes, patch)
2011-04-27 09:22 UTC, Robert Scheck
no flags Details | Diff

Description Robert Scheck 2011-04-25 23:13:59 UTC
Description of problem:
Output "Modulefile is /etc/modprobe.conf" is shown during kernel update. From
a short search, this comes from /sbin/mkinitrd. Normally, RPM-based updates or
installations should not output anything, thus this is treated as a bug.

Version-Release number of selected component (if applicable):
mkinitrd-5.1.19.6-68.el5_6.1

How reproducible:
Everytime, see above and below.

Actual results:
[...]
Running Transaction
  Installing     : kernel                                               1/4 
Modulefile is /etc/modprobe.conf
  Installing     : kmod-microsoft-hyperv-2.6.18-238.9.1.el5             2/4 
  Updating       : microsoft-hyperv                                     3/4 
  Cleanup        : microsoft-hyperv                                     4/4 
[...]

Please ignore the microsoft-hyperv modules, they are not related to this.

Expected results:
No output "Modulefile is /etc/modprobe.conf" during kernel install/upgrade.

Additional info:
I think, the "echo" should be either a "vecho" or the line should not exist
at all in /sbin/mkinitrd (overleft from debug?).

Comment 1 Robert Scheck 2011-04-25 23:22:15 UTC
I've cross-filed this issue as Service Request 00457059 and 00457061 (myself
and a customer's one).

Comment 2 Brian Lane 2011-04-25 23:54:11 UTC
This is caused by the patch for bug 564392, which should have use vecho.

Comment 3 Robert Scheck 2011-04-27 09:22:57 UTC
Created attachment 495156 [details]
mkinitrd-5.1.19.6-bz699553-correct-echo-by-vecho.patch


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