Bug 1382022 - iPXE does not Recognize SolarFlare NIC causing Provisioning to fail
Summary: iPXE does not Recognize SolarFlare NIC causing Provisioning to fail
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipxe
Version: 7.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: pre-dev-freeze
: ---
Assignee: Don Bayly
QA Contact: Ma Yuying
URL:
Whiteboard:
Depends On:
Blocks: 1401400
TreeView+ depends on / blocked
 
Reported: 2016-10-05 14:29 UTC by jpisciot
Modified: 2020-02-14 17:58 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-09 14:59:43 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description jpisciot 2016-10-05 14:29:49 UTC
Description of problem:

When booting a host to a host image boot disk, the ISO is looking for the MAC address of the SolarFlare SFC9120 NIC, however the boot image does not have the sfc kernel driver. It does not find the NIC and proceeds to fail to chain load and continue the Provisioning process

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

tfm-rubygem-foreman_bootdisk-6.1.0.3-1.el7sat.noarch
ipxe-bootimgs-20160127-1.git6366fa7a.el7.noarch

How reproducible:

Every time with the SolarFlare SFC9120 NIC connected to HP ProLiant DL360 Gen9 hardware.

Steps to Reproduce:
1. Begin with a Satellite 6.2.1 environment
2. Create new Host and fill in appropriate values (ie. RHEL 6.7 CV, NIC MAC address, host name, capsule, boot media, etc.)
3. Click Submit
4. Click on Boot Disk -> host '<hostname>' image
5. Change the boot mode of machine to Legacy BIOS in iLO of the host
6. Mount the downloaded ISO as a virtual disk and change the one time boot order to CD/DVD in ILO
7. Boot machine
8. Machine should boot to the disk and then attempt to find a network device with the given MAC address
9. Upon not finding the NIC it will pause for a few seconds and then continue through the BIOS boot order until it fails to boot or boots to another medium

Actual results:

Host does not get provisioned or even chain load to the Satellite defined boot media

Expected results:

Host to boot, chain load to the Satellite boot media, and continue along the Provisioning process - resulting in a provisioned physical host

Additional info:

Comment 3 Lukas Zapletal 2016-10-10 14:19:16 UTC
WORKAROUND: Use Full host image which is SYSLINUX-based.

Comment 6 jpisciot 2016-10-28 18:18:14 UTC
(In reply to Lukas Zapletal from comment #3)
> WORKAROUND: Use Full host image which is SYSLINUX-based.

In the environment there is no DHCP and no PXE which are requirements according to documentation.


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