Bug #32864
open
MS DHCP Bonding Provisioning Interface
Description
Hi,
I recently started creating bonds in the interface tab. First only for the non-provisioning interfaces and this works like a charm. Now I would like to also do this for the provisioning interface and here I have a strange behaviour. I'm running latest Katello 3.18.4 and a Windows DHCP with Foreman-Proxy version 2.35.
My first question is, is this actually supported?
When trying to create a bond (bond0) and attaching 2 NICS (see attachment Interfaces), the DHCP Reservation creation fails. Even if I manually delete any related DHCP reservations it breaks with an error:
Unable to save Create DHCP Settings for gedaopl04.a.space.corp task failed with the following error: ERF12-6899 [ProxyAPI::ProxyException]: Unable to set DHCP entry ([RestClient::Conflict]: 409 Conflict) for proxy http://gedasvw30.a.space.corp:8080/dhcp Failed to perform rollback on Remove DHCP Settings for gedaopl04.a.space.corp - ERF12-6899 [ProxyAPI::ProxyException]: Unable to set DHCP entry ([RestClient::Conflict]: 409 Conflict) for proxy http://gedasvw30.a.space.corp:8080/dhcp
I also attached the debug log from the windows foreman-proxy.
Thanks and Best Regards,
Oliver
Files
Updated by Jonathon Turel almost 3 years ago
- Project changed from Katello to Foreman
Updated by Lukas Zapletal almost 3 years ago
Hello,
we do not test bond configurations for provisioning. My guess it Foreman will attempt to do the DHCP reservation twice or something like that, there will be a conflict.
Updated by Oliver Weinmann almost 3 years ago
Hi Lukas,
From what I have seen is that the proxy seems to use only one of the assigned NICs MAC addresses. So that should be fine. It works just fine, for non-provisioning interfaces. For testing I removed the interface that is causing the DHCP problems eno1 from the bond and the bond was created just fine. When PXE booting the node it looks like everything is correct, but then I loose the ping to the machine. In the boot sequence I can see that the bond is created before Anaconda installer starts, I thought the bond creation would be done post the installation. For some reason it is attaching VLAN0 to the bond and this is causing a problem as my interfaces (at least the provisioning) interfaces are access ports in a different VLAN. In Foreman I have not configured a VLAN Interface on the provisioning bond. I have not yet tried to configure the interfaces as trunk with a native vlan. Maybe I give this a try next week.
Have a nice weekend
Updated by Lukas Zapletal almost 3 years ago
Foreman default templates are written in a way that if there is a bond, it configures Anaconda installer into bond too so the whole installation is also done that way. If this is not what you want, maybe we can introduce a parameter that will prevent the behavior. It makes sense for VLAN, not much for bond.