Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1489546

Summary:	(OSP-11)Ironic introspection loops over ipxe.efi for UEFI boot_mode
Product:	Red Hat OpenStack	Reporter:	Bob Fournier <bfournie>
Component:	puppet-ironic	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	mlammon
Severity:	high	Docs Contact:
Priority:	high
Version:	11.0 (Ocata)	CC:	bfournie, dcain, jjoyce, jschluet, mlammon, mlopes, mukul18, pmannidi, racedoro, slinaber, tvignaud
Target Milestone:	z4	Keywords:	Triaged, ZStream
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-ironic-10.4.1-3.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, the DHCP server configuration file for Bare Metal (ironic) inspector was not configured to handle hosts that were using UEFI and iPXE. Consequently, any host using UEFI and iPXE may have failed to boot during ironic introspection. With this update, the DHCP server file `/etc/ironic-inspector/dnsmasq.conf` was updated to handle this scenario. As a result, hosts using UEFI and iPXE can properly boot during ironic introspection.	Story Points:	---
Clone Of:	1479386	Environment:
Last Closed:	2018-02-13 16:31:14 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:
Bug Depends On:	1479386
Bug Blocks:	1489192

Comment 1 Bob Fournier 2017-10-02 16:24:38 UTC

*** Bug 1494388 has been marked as a duplicate of this bug. ***

Comment 3 Bob Fournier 2017-11-16 21:55:38 UTC

Mike - this should be the same UEFI test as was done for this bug fix as in OSP-10.

Comment 4 mlammon 2017-11-16 21:58:01 UTC

This has been verified in osp12

Comment 9 errata-xmlrpc 2018-02-13 16:31:14 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://access.redhat.com/errata/RHBA-2018:0310