Bug 1497323 – pxe booting with grubaa64.efi adds extra "-" to config filename

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1497323 - pxe booting with grubaa64.efi adds extra "-" to config filename

Summary:	pxe booting with grubaa64.efi adds extra "-" to config filename

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	grub2 (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	All Linux

Priority	high Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Peter Jones
QA Contact:	Release Test Team
Docs Contact:	Petr Bokoc

URL:
Whiteboard:
Keywords:	Patch, ZStream

Depends On:	1483740
Blocks:	1381083
	Show dependency tree / graph

Reported:	2017-09-29 14:52 EDT by Tom Lavigne
Modified:	2018-02-09 17:46 EST (History)
CC List:	17 users (show)

See Also:
Fixed In Version:	grub2-2.02-0.65.el7_4
Doc Type:	Bug Fix
Doc Text:	A bug in the GRUB2 boot loader caused a trailing "-" character to be added to the client MAC address when attempting to load configuration files from a tftp server during PXE boot. This update fixes the bug, and clients can now load their GRUB2 configuration files from tftp servers successfully.
Story Points:	---
Clone Of:	1483740
Environment:
Last Closed:	2017-10-19 11:17:12 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:2950	normal	SHIPPED_LIVE	grub2 bug fix update	2017-10-19 14:51:37 EDT

Groups: None (edit)

Description Tom Lavigne 2017-09-29 14:52:45 EDT

This bug has been copied from bug #1483740 and has been proposed
to be backported to 7.4 z-stream (EUS).

Comment 11 errata-xmlrpc 2017-10-19 11:17:12 EDT

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-2017:2950

Note You need to log in before you can comment on or make changes to this bug.