Bug 1387322

Summary:	Redundant "dhcp" command in the iPXE scripts slows down and may actually break the boot
Product:	Red Hat OpenStack	Reporter:	Dmitry Tantsur <dtantsur>
Component:	openstack-ironic	Assignee:	Dmitry Tantsur <dtantsur>
Status:	CLOSED ERRATA	QA Contact:	Raviv Bar-Tal <rbartal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	10.0 (Newton)	CC:	dbecker, ddomingo, jschluet, mburns, morazi, rbartal, rhel-osp-director-maint, srevivo
Target Milestone:	rc	Keywords:	Triaged
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ironic-6.2.1-4.el7ost puppet-ironic-9.4.1-1.el7ost	Doc Type:	Bug Fix
Doc Text:	This release removes a redundant 'dhcp' command from the iPXE templates for deployment and introspection. In some cases, this redundant command caused an incorrect interface to receive an IP address.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-14 16:23:56 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:
Embargoed:

Description Dmitry Tantsur 2016-10-20 15:55:17 UTC

For quite some time I was wondering why we need "dhcp" in both introspection and deployment iPXE scripts. By this moment we obviously already have an IP address, so this just slows down everything.

However, today I've found an environment where this command is breaking introspection. It turns out that it uses the first NIC unconditionally, thus breaking fetching images from the second NIC.

I suggest removing this command.

Comment 1 Dmitry Tantsur 2016-11-18 15:09:04 UTC

Somehow, I've lost track of this bug. It's fixed.

Comment 3 Jon Schlueter 2016-11-18 18:01:28 UTC

https://review.openstack.org/#/c/392556/ is in puppet-ironic-9.4.1-1.el7ost
https://review.openstack.org/#/c/392552/ is in openstack-ironic-6.2.1-4.el7ost

Comment 7 errata-xmlrpc 2016-12-14 16:23:56 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2948.html