Bug 1378097

Summary:	UEFI discovered nodes fails to boot: dhcpd.conf is not set properly
Product:	Red Hat Satellite	Reporter:	Lukas Zapletal <lzap>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Jan Hutař <jhutar>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3.0	CC:	bbuckingham, ehelms, jcallaha, jhutar, stbenjam
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	https://github.com/theforeman/puppet-dhcp/pull/82
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 17:07:53 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 Lukas Zapletal 2016-09-21 13:30:34 UTC

The following change is needed for discovery UEFI support which currently does not work (UEFI discovered hosts fail to load).

https://github.com/theforeman/puppet-dhcp/pull/82

QA: Check dhcpd.conf, it used to be:

next-server 192.168.222.1;
filename "pxelinux.0";

Now it should look like (ignore the quotes and plus):

 +            'option architecture code 93 = unsigned integer 16 ;',
 +            'if option architecture = 00:00 {',
 +            '  filename "pxelinux.0";',
 +            '} elsif option architecture = 00:06 {',
 +            '  filename "shim.efi";',
 +            '} elsif option architecture = 00:07 {',
 +            '  filename "shim.efi";',
 +            '} elsif option architecture = 00:09 {',
 +            '  filename "shim.efi";',
 +            '} else {',
 +            '  filename "pxelinux.0";',
 +            '}',

Comment 2 Bryan Kearney 2016-10-13 16:16:20 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/14920 has been resolved.

Comment 4 Bryan Kearney 2018-02-21 17:07:53 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/RHSA-2018:0336