On 29 October 2016 at 11:51, Alexander Rilik <[email protected]> wrote:
> On Friday, October 28, 2016 at 11:31:54 PM UTC+2, Greg Sutcliffe wrote: > >> So, that comes from a fairly convoluted process, but the core is this - >> which TFTP smart proxy is assigned to the host's subnet in the Foreman UI? >> > > The right smart proxy! > Here's what I tried, without success: > - unset discovery proxy from subnet, set proxy on subnet again > - delete subnet > - import subnet from scratch from the dhcp/tftp/discovery proxy > Interesting. What should happen is this: * A host has a provisioning interface * That interface has a subnet * That subnet has a tftp proxy * That tftp proxy has a config option - :tftp_servername: * The name or IP in that setting is what is written to the DHCP lease So, if the proxy is right, then I'd check that setting on the appropriate proxy. I'd also recommend using an IP there, if it's not already. DNS can make a mess here unless you're careful. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
