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

Bug 1609796

Summary:	[RFE] Split ironic ipxe/pxe interfaces to enable multi-arch deployments
Product:	Red Hat OpenStack	Reporter:	Julia Kreger <jkreger>
Component:	openstack-ironic	Assignee:	Julia Kreger <jkreger>
Status:	CLOSED ERRATA	QA Contact:	mlammon
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	bfournie, mburns, racedoro, sasha, srevivo
Target Milestone:	Upstream M2	Keywords:	FutureFeature, TechPreview, Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ironic-12.1.2-0.20190615000404.c3cbdb5.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:16:20 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 Julia Kreger 2018-07-30 13:28:54 UTC

Description of problem:

Presently mixed architecture environments must disable iPXE as only iPXE binaries are provided for x86_64 hardware. One _can_ build an ARM iPXE binary, but otherwise the only other option for ARM hardware is GRUB2.

Similarly, ppc64le hardware has a bootloader which reads and interprets syslinux style templates that Ironic creates to perform network booting. That forces operators to globally disable iPXE for both ppc64le and x86_64 hardware.

It has been proposed previously to split the PXE and iPXE boot interfaces. Initial patches are available upstream.

Comment 1 Bob Fournier 2018-08-15 18:49:09 UTC

Marking for consideration in OSP-15, remove if not feasible.

Comment 6 Dmitry Tantsur 2019-01-04 15:41:00 UTC

Complete on ironic side, needs tripleo bits.

Comment 7 Bob Fournier 2019-01-09 02:32:33 UTC

Tripleo patches have merged, moving to POST.

Comment 11 errata-xmlrpc 2019-09-21 11:16:20 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/RHEA-2019:2811