Hey Craig and welcome here. Can you explain what happens in more detail? At which point you seem to lost IP address? You say you hit kickstart that would mean Anaconda was loaded up and initialized network, at this point there is almost nothing which could literally stop Anaconda from completing installation, except some misconfiguration in the kickstart itself.
Also which bootdisk type do you use? These are very different workflows. Generic (and subnet) bootdisks match the host you want to provision with MAC address. But host or full host disk uses token which is tied to host you created bootdisk for. The token has limited expiration time (by default 90 minutes I think), then the bootdisk is invalid. You can turn of token_duration in settings, in that case Foreman will try to match hosts via REMOTE_IP (which will not work if your IP address is not correct in foreman db) or for Anaconda (Red Hat systems only) it will match according to MAC address sent by anaconda in HTTP header. Better understanding will give you generic and host snippets which are used to generate /SCRIPT file for iPXE: https://github.com/theforeman/foreman_bootdisk/blob/master/app/views/foreman_bootdisk/generic_host.erb https://github.com/theforeman/foreman_bootdisk/blob/master/app/views/foreman_bootdisk/host.erb For full host disk PXELinux template is used. Remember you can edit any of these in Foreman, feel free to modify iPXE as you want. If you don't want static allocation, you can just put DHCP statement there and iPXE will chainboot from Foreman iPXE template using DHCP. The same way you can modify PXELinux template which is by default DHCP (but when Subnet is put into Static mode it will also use static configuration). In all cases, I recommend to setup this without foreman first and then after full understanding how you want piece things together you can modify templates like you want. Good luck! On Tue, Oct 10, 2017 at 9:15 AM, Craig Parker <[email protected]> wrote: > Hi everybody, and thanks Foreman people for a wonderful piece of kit. I've > been using it successfully for a little while, and am now trying to sort out > provisioning here at work to save us some time. > > We are predominantly a Windows environment however, and in particular our > DHCP servers are windows boxes that I have no control over. PXE is in use > exclusively for our Windows imaging. > > Given that, I though that the foreman_bootdisk plugin would be the answer, > and I'm really close to getting it all working, but any machine I try to > provision has network issues and fails the build. I boot via the generic boot > disk and the machine starts, gets an IP address and contacts The Foreman for > build instructions (preseed, kickstart etc). After that it seems that the > machine loses its IP address and subsequently fails to go any further. > > I think the piece I'm missing is how to make The Foreman bootdisk scenario > work with an external DHCP server. I had thought I could just boot via the > bootdisk and let the existing DHCP take care of the network piece, and this > is exactly how I build RHEL boxes here from Satellite 5.x, but I think I've > missed some config or I'm not understanding how Foreman works with external > non-controlled DHCP. > > Apologies for the long post. Can anyone offer any guidance on how to make > Foreman bootdisk and external DHCP work? More than happy to provide any > details or logs that could be of use. > > Many thanks, Craig. > > -- > 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. -- Later, Lukas @lzap Zapletal -- 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.
