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 1044623 - dracut always uses BOOTIF if defined.
Summary: dracut always uses BOOTIF if defined.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: dracut-maint
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 17:17 UTC by Bill Peck
Modified: 2020-09-09 11:55 UTC (History)
8 users (show)

Fixed In Version: dracut-033-84
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 10:06:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5384271 0 None None None 2020-09-09 11:55:52 UTC

Description Bill Peck 2013-12-18 17:17:56 UTC 
Description of problem:

dracut always uses BOOTIF if present on the command line.  The real problem is that pxe configs need ipappend 2 in order for pxelinux.0 to send BOOTIF=<MAC>.  But there is no way to edit this when booting a system from the pxe menu.  In the past if we had ksevice=bootif on the append line and needed to change it we could simply edit the append line to ksdevice=<MAC> or remove it entirely (while at the systems console).

Now the only way to change this is to go back to the tftpboot server and edit the text file.


Version-Release number of selected component (if applicable):
dracut-033-40.el7

How reproducible:
everytime

Expected results:
some way to disable/change BOOTIF without having to remove ipappend 2 from the pxe config file.
Comment 3 Harald Hoyer 2013-12-19 10:48:53 UTC 
(In reply to Bill Peck from comment #0)
> Description of problem:
> 
> dracut always uses BOOTIF if present on the command line.  The real problem
> is that pxe configs need ipappend 2 in order for pxelinux.0 to send
> BOOTIF=<MAC>.  But there is no way to edit this when booting a system from
> the pxe menu.  In the past if we had ksevice=bootif on the append line and
> needed to change it we could simply edit the append line to ksdevice=<MAC>
> or remove it entirely (while at the systems console).
> 
> Now the only way to change this is to go back to the tftpboot server and
> edit the text file.
> 
> 
> Version-Release number of selected component (if applicable):
> dracut-033-40.el7
> 
> How reproducible:
> everytime
> 
> Expected results:
> some way to disable/change BOOTIF without having to remove ipappend 2 from
> the pxe config file.

like rd.bootif=0 ?

Hmm, thinking about it. Does appending "BOOTIF=" at the end work?
Comment 4 Bill Peck 2013-12-19 11:46:48 UTC 
we tried adding the other nic's mac address to BOOTIF= but that didn't seem to work.  I can do it again and report the order that the entries end up in command line.
Comment 6 Harald Hoyer 2014-01-17 16:33:30 UTC 
dracut-033-84
Comment 8 Ľuboš Kardoš 2014-01-30 07:43:10 UTC 
Verified on RHEL-7.0-20140127.0. When I add rd.bootif=0 all network interfaces are activated not only BOOTIF interfaces.
Comment 9 Ľuboš Kardoš 2014-01-30 07:55:57 UTC 
Verified on dracut-033-85.
Comment 10 Ludek Smid 2014-06-13 10:06:38 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.