Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix next-server behavior #3540

Merged
merged 1 commit into from
Jan 13, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 2 additions & 10 deletions guides/common/modules/ref_options-in-managed-dhcpv4.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,16 +17,8 @@ Each TFTP {SmartProxy} then reports this setting through the API and {Project} c
+
When the PXE loader is set to `none`, {Project} does not populate the `next-server` option into the DHCP record.
+
If the `next-server` option remains undefined, {Project} uses reverse DNS search to find a TFTP server address to assign, but you might encounter the following problems:

* DNS timeouts during provisioning
* Querying of incorrect DNS server.
For example, authoritative rather than caching
* Errors about incorrect IP address for the TFTP server.
For example, `PTR record was invalid`

+
If you encounter these problems, check the DNS setup on both {Project} and {SmartProxy}, specifically the PTR record resolution.
If the `next-server` option remains undefined, {Project} calls the {SmartProxy} API to retrieve the server name as specified by the `--foreman-proxy-tftp-servername` argument in a `{foreman-installer}` run.
If the {SmartProxy} API call does not return a server name, {Project} uses the hostname of the {SmartProxy}.

`filename`::
The `filename` option contains the full path to the file that downloads and executes during provisioning.
Expand Down