- Can’t provision a server to a network not associated with the DHCP subnet.
- I would like to be able to create a subnet (outside of the DHCP range) to be able to provision servers with networking across a very large number of subnets.
Foreman and Proxy versions:
[root@master dhcpd]# hammer --version hammer (0.3.0) * hammer_cli_foreman (0.3.0) * hammer_cli_foreman_discovery (0.0.2)
Other relevant data:
- It seems that Foreman expects the subnet to be configured @ install. Would this mean that I have to configure every subnet in the datacenter on install? What if new subnets are created?
[28/Mar/2019:12:25:31 -0400] "GET /tftp/serverName HTTP/1.1" 200 29 0.0013 E, [2019-03-28T12:25:31.300606 #23246] ERROR -- : Record not found E, [2019-03-28T12:25:31.541569 #23246] ERROR -- : No Subnet detected for: "$NETWORK_ADDRESS"
- On GUI
Unable to save Create DHCP Settings for mac0025904788ea task failed with the following error: ERF12-6899 [ProxyAPI::ProxyException]: Unable to set DHCP entry ([RestClient::BadRequest]: 400 Bad Request) for proxy https://foreman:8443/dhcp
- Using the primary subnet that is configured for DHCP works fine.
- My user story is I just want to be able to provision servers with no plans for using Foreman for anything else at the moment.
- The logic would be, auto-discover the server via a DHCP private range, api to create the subnet, provision the server with an IP address that could be 1 of 100s/1000s of subnets, then delete the host/subnet from Foreman. Is this possible with Foreman other than having to re-install every time?