I would like to use foreman + discovery for bare metal provisioning
(version 1.11).
When I push the button "Auto provision all" in the "Discovered hosts"
section all these nodes reboot (fine), but NO pxelinux.cfg/… file was
created.
Even in debug mode, proxy.log does not show anything about this. That
indicates that the foreman has got some problems here.
(There is no problem with manual provisioning, though. But that takes time.)
Two things:
Where can I see what is missing?
Wouldn't it be better to warn the user that something is missing than
rebooting the nodes without effect?
> Hello,
>
> I would like to use foreman + discovery for bare metal provisioning
> (version 1.11).
>
> When I push the button "Auto provision all" in the "Discovered hosts"
> section all these nodes reboot (fine), but NO pxelinux.cfg/… file was
> created.
>
that probably means your subnet doesn't have a tftp proxy associated.
Even in debug mode, proxy.log does not show anything about this. That
> indicates that the foreman has got some problems here.
>
Thats good feedback, and you should probably add it as a feature request on http://projects.theforeman.org - and of course -patches are welcomed
thanks!
···
On Wed, Jun 1, 2016 at 3:52 PM, 'Ulf Markwardt' via Foreman users < foreman-users@googlegroups.com> wrote:
(There is no problem with manual provisioning, though. But that takes
time.)
Two things:
Where can I see what is missing?
Wouldn’t it be better to warn the user that something is missing
than rebooting the nodes without effect?
>> I would like to use foreman + discovery for bare metal provisioning
>> (version 1.11).
>>
>> When I push the button "Auto provision all" in the "Discovered hosts"
>> section all these nodes reboot (fine), but NO pxelinux.cfg/… file was
>> created.
>>
>
> that probably means your subnet doesn't have a tftp proxy associated.
>
But it does, I have checked!
Interesting: "Smart Proxy => Services" says "TFTP server false", yet I
can manually provision my hosts.