Bug #14905
closed
DHCP reservation for PXE boot not added when using static boot mode
Added by Jan-Otto Kröpke over 8 years ago.
Updated over 6 years ago.
Description
Hi,
we have one central tftp server and multiple dhcp servers to avoid the dhcp relay via firewalls.
Since foreman 1.11, we can not deploy vm, because foreman will not add the dhcp leases on the external dhcp servers. PXE will not work anymore.
tcpdump also wont show any connections..
If I add a tftp role to a dhcp server and attach it to one subnet, the leases will be added to this dhcp server doing the host creation and everything will be work as expected.
I can not find any errory on /var/log/foreman-proxy/proxy.log or /var/log/foreman/production.log .
Best Regards,
Jan-Otto Kröpke
noris network AG
Files
I have attached two screenshot
One from installing a machine.
An another screenshot from the subnet setting.
As you can see, the step "configure dhcp" is missing on the first screen.
Looks like foreman ignore the settings from the subnet.
Unset and set the settings again does not work correctly.
We are upgrade to foreman 1.11 and then to 1.11.1. Maybe there are some migrations issues.
- Project changed from Smart Proxy to Foreman
- Category changed from DHCP to DHCP
- Status changed from New to Need more information
What is the Boot mode set to in the Subnet settings? Ensure it's on DHCP, not Static.
It is Static and it work since 1.6 without any problems.
The subnet which has the foreman as TFTP and DHCP proxy itself,
If Static is a problem, how to deploy PXE machines?
- Related to Bug #14113: DHCP orchestration ignored subnet bootmode added
- Status changed from Need more information to Feedback
It is Static and it work since 1.6 without any problems.
The linked bug changes behaviour to only create DHCP reservations when DHCP boot mode is in use. You should consider changing the boot mode to DHCP, which should fix PXE booting.
Its does not make sense.
PXE should work even with Static Boot mode. In my opinion, provision and boot mode are two different things.
Using DHCP as boot mode is fatal, because if the foreman is unavailable, all maschine will drop the ip after the lease time..
The Foreman will mutate to a single point of failure.
- Subject changed from Foreman does not add dhcp.leases for new vm, if dhcp and tftp proxy is different to DHCP reservation for PXE boot not added when using static boot mode
- Status changed from Feedback to New
PXE should work even with Static Boot mode. In my opinion, provision and boot mode are two different things.
Yes, I'll leave this bug open for that reason.
Using DHCP as boot mode is fatal, because if the foreman is unavailable, all maschine will drop the ip after the lease time..
As an aside, DHCP is provided by your DHCP server and not Foreman, so could well be set up in a failover or other HA configuration.
Thanks.
Maybe a configable option would be the best.
I confirm hitting the same issue.
In our setup, we are using DHCP for provisionning, but static IP addressing for the servers once they are online.
We still want the lease to be created to support the provisionning process as well as recovery environnements.
- Translation missing: en.field_release set to 155
- Translation missing: en.field_release changed from 155 to 159
I confirm too, we use dhcp server only in "static" mode. The dhcp server is only used for provisioning purposes (DHCP/PXE/TFTP) and keep track of already assigned IPs on our subnets with dhcp reservations.
- Related to Support #14792: foreman not sending the POST to the DHCP smart proxy added
- Status changed from New to Ready For Testing
- Assignee set to Dominic Cleal
- Pull request https://github.com/theforeman/foreman/pull/3552 added
As workaround I edited the snippet "kickstart_networking_setup" and added
<% dhcp = false >
below
< dhcp = subnet.dhcp_boot_mode? -%>
in line 113.
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Bugzilla link set to 1340167
Also available in: Atom
PDF