Distinguish between HTTP booting stages #4304
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Needs tech review
maximiliankolb
requested changes
Sep 25, 2025
guides/common/modules/con_uefi-http-booting-requirements-with-managed-dhcp.adoc
Outdated
Show resolved
Hide resolved
guides/common/modules/proc_configuring-smart-proxy-for-http-booting.adoc
Outdated
Show resolved
Hide resolved
pr-processor
bot
added
Waiting on contributor
jloeser
force-pushed
the
fix/http-booting
branch
from
32f53e6 to
e6b0e6e
Compare
jloeser
force-pushed
the
fix/http-booting
branch
from
e6b0e6e to
c7eeabe
Compare
|
@stejskalleos Can you please review this? |
stejskalleos
approved these changes
Oct 7, 2025
Lennonka
added
tech review done
maximiliankolb
added
style review done
|
@jloeser Please rebase your branch to HEAD of "master" and resolve the merge conflicts. |
jloeser
force-pushed
the
fix/http-booting
branch
from
c7eeabe to
97f98f7
Compare
|
I rebuilt/tested documentation locally and it LGTM. |
|
Looks like we need some technical adaptions regarding HTTPS - it simply does not work at all with GRUB2. I will take care ... |
During network based provisioning, there are two stages where either TFTP or HTTP(S) can be used: fetching the boot loader and fetching installation files such as Linux kernel and initrd. Both were partly mixed, partly incomplete, and instructions were ambiguous or did not work.
jloeser
force-pushed
the
fix/http-booting
branch
from
97f98f7 to
325cc8c
Compare
|
Related: theforeman/foreman#10718 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During network based provisioning, there are two stages where either TFTP or HTTP(S) can be used: fetching the boot loader and fetching installation files such as Linux kernel and initrd.
Both were partly mixed, partly incomplete, and instructions were ambiguous or did not work.
What changes are you introducing?
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Contributor checklists
Please cherry-pick my commits into: