Bug 1044623

Summary: dracut always uses BOOTIF if defined.
Product: Red Hat Enterprise Linux 7 Reporter: Bill Peck <bpeck>
Component: dracutAssignee: dracut-maint
Status: CLOSED CURRENTRELEASE QA Contact: Release Test Team <release-test-team>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: dracut-maint-list, harald, jburke, jstodola, lkardos, ncoghlan, pbunyan, rmetrich
Target Milestone: rcKeywords: TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dracut-033-84 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 10:06:38 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:

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.