undercloud didn't find network device while pxe boot

Bug #1848546 reported by Валерия Валерьевна Швецова
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
New
Undecided
Unassigned

Bug Description

Description
===========
I have installed undercloud with all default settings using packages from https://trunk.rdoproject.org/centos7-stein/26/76/26765458ef4f3999e09ebf5d9ac84d4abf841d75_73ce9be8 , created some baremetal nodes with following settings

~~
nodes:
  - name: node-[num]
    pm_type: idrac
    pm_addr: 10.100.1.6
    pm_user: *
    pm_password: *
    capabilities: boot_mode:uefi
    ports:
      - address: *
~~

The nodes successfully created, then I tried to execute `openstack overcloud node introspect`, and some nodes were inspected successfully and some of them failed while pxe boot. The failed nodes screen show the following

~~
>>Start PXE over IPv4
  Station IP address is 192.168.24.107

  Server IP address is 192.168.24.1
  NBP filename is ipxe.efi
  NBP filesize is 741120 Bytes
Downloading NBP file..

  Succees to download NBP file.
iPXE initialising devices..ok

iPXE 1.0.0.+ (133f4c) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP iSCSI TFTP SRP VLAN AoE EFI Menu

No more network devices
~~

Then boot failes and continue booting another way

Steps to reproduce
==================

* Install undercloud using https://trunk.rdoproject.org/centos7-stein/26/76/26765458ef4f3999e09ebf5d9ac84d4abf841d75_73ce9be8
* Create baremetal nodes
* Execute ironic introspection

Expected result
===============
All nodes successfull introspection

Actual result
=============
Some nodes failes PXE boot

Environment
===========
1. OpenStack Stein

2. Failed servers from blade server DELL PowerEdge M630 and M640

3. Successfully booted servers from blade server DELL PowerEdge R630 and R640

Logs & Configs
==============

Logs don't contain any errors, the only difference between failed and successfull nodes is that failed nodes has two macs (chassis-assigned and server-assigned) for every port, etc

Revision history for this message
Валерия Валерьевна Швецова (versus-vv) wrote :

The problem is in new file ipxe.file, which is sent to the machine by Ironic service

This conclusion was made because using old ipxe.efi instead of new one solves the problem

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.