Updated checklist: - host is managed *- yes - OK* - provision method is "build" and not "image" *- I can't see the 'build mode' checkbox for the newly created host* - host has operating system set *- yes (inherited from host group) - OK* - host has pxe loader flag present (not set to blank or None) *- yes - OK* - host has one provisioning NIC with valid MAC address *- yes - OK* - a subnet is associated with the provisioning NIC *- it is - OK* - the subnet has TFTP feature turned on *- it does - OK*
Other issues with auto-provision: - hostname doesn't match discovery rule pattern (correct pattern being visible on host list, but then I click edit and see 'macXXXXXX') - discovery interface DNS name doesn't match discovery rule pattern (correct pattern being visible on host list, but then I click edit->interfaces->edit and see 'macXXXXXX') - no domain assigned to discovery interface, despite domain attached to discovery subnet I have tried to use subnet without domain assigned (no effect). PXE file for auto-provisioned host does NOT get created, no matter what I do... In this state, whole 'auto-provision' brings no value to the table :( W dniu czwartek, 13 kwietnia 2017 16:36:52 UTC+2 użytkownik Garreat napisał: > > I experience this issue. > After clicking 'auto-provisioning' on a discovered host, the host entry is > created, the host reboots - but only to enter Foreman Discovery Image PXE > loop. > My TFTP proxy is in healthy status as I can recreate PXE default no prob. > > Now answering your checklist: > - host is managed *- yes - OK* > - provision method is "build" and not "image" *- how to check this? I > can't see the 'build mode' checkbox for the newly created host* > - host has operating system set - yes (inherited from host group) *- OK* > - host has pxe loader flag present (not set to blank or None) *- how to > check this?* > - host has one provisioning NIC with valid MAC address *- yes it does - > OK* > - a subnet is associated with the provisioning NIC *- it is, but it's a > subnet different than the one declared in machine's host group* > - the subnet has TFTP feature turned on *- it does, and it's the same > TFTP proxy as in the subnet that I wanted* > > Also, the 'domain' is blank for the fresh created host. > The OS assigned to this host group has a valid PXElinux template selected. > > Assume I'm not making any manual changes: > - 'Build host' does nothing > - 'Rebuild config' creates a PXE mac-template on TFTP immediatly > > facter -j output attached > > Thanks / Regards / Greetings > > W dniu wtorek, 11 kwietnia 2017 10:28:17 UTC+2 użytkownik Lukas Zapletal > napisał: >> >> TFTP orchestration is not being triggered. It can be only performed >> when all of these conditions are met: >> >> - host is managed >> - provision method is "build" and not "image" >> - host has operating system set >> - host has pxe loader flag present (not set to blank or None) >> - host has one provisioning NIC with valid MAC address >> - a subnet is associated with the provisioning NIC >> - the subnet has TFTP feature turned on >> >> Visit a host which failed provisioning and do this checklist please. >> >> LZ >> >> >> -- 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.
