From b52faff2bcfa2b3e7f59a44b48287048f11d19fc Mon Sep 17 00:00:00 2001 From: Lennonka Date: Tue, 14 Jan 2025 15:56:40 +0000 Subject: [PATCH] deploy: dd41db4b0be7cf31a6319ecd357c82d2f91e4f40 --- 3.11/Provisioning_Hosts/index-katello.html | 21 ++----------------- 3.11/Provisioning_Hosts/index-orcharhino.html | 21 ++----------------- 3.11/Provisioning_Hosts/index-satellite.html | 21 ++----------------- 3 files changed, 6 insertions(+), 57 deletions(-) diff --git a/3.11/Provisioning_Hosts/index-katello.html b/3.11/Provisioning_Hosts/index-katello.html index d7f7cec1ad..f4d740d1a6 100644 --- a/3.11/Provisioning_Hosts/index-katello.html +++ b/3.11/Provisioning_Hosts/index-katello.html @@ -2681,25 +2681,8 @@

-

If the next-server option remains undefined, Foreman 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 Foreman and Smart Proxy, specifically the PTR record resolution.

+

If the next-server option remains undefined, Foreman calls the Smart Proxy API to retrieve the server name as specified by the --foreman-proxy-tftp-servername argument in a foreman-installer run. +If the Smart Proxy API call does not return a server name, Foreman uses the hostname of the Smart Proxy.

The filename option
diff --git a/3.11/Provisioning_Hosts/index-orcharhino.html b/3.11/Provisioning_Hosts/index-orcharhino.html index e70613b61d..d7d32a690f 100644 --- a/3.11/Provisioning_Hosts/index-orcharhino.html +++ b/3.11/Provisioning_Hosts/index-orcharhino.html @@ -2791,25 +2791,8 @@

-

If the next-server option remains undefined, orcharhino 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 orcharhino and orcharhino Proxy, specifically the PTR record resolution.

+

If the next-server option remains undefined, orcharhino calls the orcharhino Proxy API to retrieve the server name as specified by the --foreman-proxy-tftp-servername argument in a foreman-installer run. +If the orcharhino Proxy API call does not return a server name, orcharhino uses the hostname of the orcharhino Proxy.

The filename option
diff --git a/3.11/Provisioning_Hosts/index-satellite.html b/3.11/Provisioning_Hosts/index-satellite.html index 6d2aae1f3e..8c4390aabe 100644 --- a/3.11/Provisioning_Hosts/index-satellite.html +++ b/3.11/Provisioning_Hosts/index-satellite.html @@ -2332,25 +2332,8 @@

-

If the next-server option remains undefined, Satellite 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 Satellite and Capsule, specifically the PTR record resolution.

+

If the next-server option remains undefined, Satellite calls the Capsule API to retrieve the server name as specified by the --foreman-proxy-tftp-servername argument in a satellite-installer run. +If the Capsule API call does not return a server name, Satellite uses the hostname of the Capsule.

The filename option