Bug 1715185 - PXE boot ignores statement like ip:eno2:dhcp
Summary: PXE boot ignores statement like ip:eno2:dhcp
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RHCOS
Version: 4.1.0
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.1.z
Assignee: Steve Milner
QA Contact: Micah Abbott
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-29 19:06 UTC by William Caban
Modified: 2019-05-30 13:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-30 13:15:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description William Caban 2019-05-29 19:06:34 UTC
Description of problem:
When using pxe boot in a bare-metal system with multiple interfaces, dracut ignores something like ip:eno2:dhcp and it tries DHCP on all interfaces

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

openshift-install-linux-4.1.0-rc.5
rhcos-410.8.20190516.0-metal-bios.raw.gz


How reproducible:

100% of the time in bare-metal

Actual results:

It sends DHCP request over every interface and waits for a timeout. If the system has a lot of interfaces the NetworkManager-wait-online.service process fails and create a cascade failure during the bootstrap process.

Expected results:

To ignore all the other interfaces

Comment 1 Dusty Mabe 2019-05-29 19:16:47 UTC
> dracut ignores something like ip:eno2:dhcp

I assume you mean `ip=eno2:dhcp` ?

Comment 2 William Caban 2019-05-29 20:03:43 UTC
correct. like this:

  APPEND ip=eno2:dhcp ipv6.disable=1 rd.neednet=1 initrd=rhcos/rhcos-initramfs.img console=tty0 console=ttyS0 coreos.inst=yes coreos.inst.install_dev=sda coreos.inst.ignition_url=http://192.168.1.1:8000/bootstrap.ign coreos.inst.image_url=http://192.168.1.1:8000/metal/rhcos-410.8.20190516.0-metal-bios.raw.gz

Comment 3 Steve Milner 2019-05-30 13:15:58 UTC
Per the debug session yesterday it's been noted ip=eno2:dhcp is acting like it should. Closing this bug.


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