RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Hello,

I am trying to configure UEFI HTTP Boot over IPv6 with Grub2. Here is my dhcp config:

option dhcp6.bootfile-url code 59 = string;
option dhcp6.vendor-class code 16 = {integer 32, integer 16, string};

subnet6 2001:db8:f00f:cafe::/64 {
 range6 2001:db8:f00f:cafe::42:10 2001:db8:f00f:cafe::42:99;
 option dhcp6.bootfile-url "http://[2001:db8:f00f:cafe::1]/httpboot/grub2/grubx64.efi";
 option dhcp6.name-servers 2001:db8:f00f:cafe::1;
 option dhcp6.vendor-class 0 10 "HTTPClient";
}

Grub2 loads fine, loads configuration which is:

set default=0
set timeout=10
menuentry 'Kickstart default PXEGrub2' {
  linuxefi boot/centos-local-proxy-NpAPvFVIy69k-vmlinuz ks=http://sat66.nat.lan/unattended/provision?token=d716ee59-fabf-40f6-8b21-9a6a14c47c2e  network ksdevice=bootif ks.device=bootif BOOTIF=00-00-c0-3a-d1-01-8f kssendmac ks.sendmac inst.ks.sendmac BOOTIF=01-$net_default_mac
  initrdefi boot/centos-local-proxy-NpAPvFVIy69k-initrd.img
}

However after the timeout there is a network error. Depending on bootfile-url it's different:

For http://[2001:db8:f00f:cafe::1] I get: unrecognised network address '2001:db8:f00f:cafe::1', unsupported uefi http status code 0x11, fail to receive a reponse! status=104

For http://ipv6_only_hostname I get: unrecognised network address 'ipv6_only_hostname'

Is IPv6 supported in this scenario? Thanks.

With most recent grub2-2.02-0.80.el7 I only get "unrecognised network address" error. Looks like there is a message "Press any key to continue..." and after a short delay the system boots up. I made a photo of this.

Not sure if this is relevant, but *randomly* grub2 also fails to load the file with "invalid magic number". This happens on LAN and this is HTTP Boot so unlikely a TFTP packet drop. Attaching too.

Created attachment 1665899 [details]
Libvirt VM screenshot

I was able to reproduce this issue and the problem was that GRUB was not enclosing the literal IPv6 address in square brackets when writing the Host field of the HTTP request header.

Reproduced on RHEL-7.8-20200225.1 x86_64 Server

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

Reproduced using RHEL-7.8
Verified using RHEL-7.9-20200623.0 with grub2-2.02-0.82.el7, both IPv6 and hostname cases work fine now.

Moving to VERIFIED.

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-2020:3217