Bug 1388575

Summary: Grub HTTP support
Product: [Fedora] Fedora Reporter: Christopher Covington <ccovingt>
Component: grub2Assignee: Peter Jones <pjones>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: ccovingt, lkundrak, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:35:30 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:

Description Christopher Covington 2016-10-25 17:20:18 UTC
Please build HTTP support into Grub.

Grub is currently built with TFTP support. This enables short-distance/low-latency network boot. Unfortunately TFTP performs poorly at long-distance/high-latency. Compared to TFTP, HTTP requires less back-and-forth between client and server and therefore works faster and more reliably (as its less likely to time out) at long-distance/high-latency. With HTTP it also becomes easy to deploy caching proxies at remote endpoints.

Here is an example grub.cfg using hard-coded HTTP IP addresses:

linux (http,1.2.3.4)/fed/25/Server/aarch64/os/images/pxeboot/vmlinuz ks=http://webserver/fed.ks
initrd (http,1.2.3.4)/fed/25/Server/aarch64/os/images/pxeboot/initrd.img
boot

In cases where the DHCP server and UEFI are recent enough and properly configured for HTTP boot, the IP address or hostname of the HTTP server need not be hard-coded into the grub.cfg. Rather (http)/path/to/file or the implicit $root can be used.

Comment 1 Fedora End Of Life 2017-02-28 10:30:49 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 2 Fedora End Of Life 2018-05-03 08:23:33 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 11:35:30 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.