Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1069275

Summary: dracut-004-336 issues when ifname is not specified as kernel parameter
Product: Red Hat Enterprise Linux 6 Reporter: Marius Boeru <marius.boeru>
Component: dracutAssignee: Harald Hoyer <harald>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6CC: dracut-maint-list, harald, jonathan, mganisin, mkovarik
Target Milestone: rc   
Target Release: 6.6   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: if "ip=ibft" is specified as a kernel command line argument, but no "ifname=<iface>:<mac>", dracut does not handle network interfaces. Consequence: iSCSI disks will not be connected to the system and the system does not boot. Fix: dracut now handles "ip=ibft" as a kernel command line argument, even without "ifname=<iface>:<mac>". Result: iSCSI disks will be connected to the system and the system boots.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 06:37:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Proposed patch none

Description Marius Boeru 2014-02-24 16:14:10 UTC
Description of problem:
if no ifname is specified as kernel argument the server will not boot using ip=ibft. It will not find iscsi the root device

Version-Release number of selected component (if applicable): CentOS 6.5


How reproducible:


Steps to Reproduce:
1.Install CentOS using netinstall iso on an iscsi lun
2. after instalation remove ifname=eth0:XX:XX:XX:XX:XX:XX from kernel line
3. try to boot and it will fail

Actual results:
rdinitdebug boot log and init.log: http://pastebin.com/XY4Ahwam

Expected results:
The OS should be able to boot only with ip=ibft and no ifname parameter

Additional info:
fix by haraldh: http://paste.fedoraproject.org/79831/32523561/

dirty fix: set ifname=dummy:FF:FF:FF:FF:FF:FF (or anything else in the same format) as a parameter and the OS will boot from iscsi and will set ibft0 accordingly

Comment 1 Harald Hoyer 2014-02-24 16:22:53 UTC
Created attachment 867046 [details]
Proposed patch

Comment 4 errata-xmlrpc 2015-07-22 06:37:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1328.html