I was actually having similar issues with it this week, another issue is using the "hammer" cli to provision the host with a specific interface configuration (i suspect it's related as we have a similar configuration) $ hammer discovery provision \ --id=80 \ --build=1 \ --enabled=1 \ --managed=1 \ --hostgroup-id=9 \ --new-name=server1 \ --owner-id=4 \ --provision-method=build \ --interface="type=bond,mac=0c:c4:74:b3:9c:ba,identifier=bond0,name=server1,domain_id=1,subnet_id=11,ip=172.14.20.13,managed=true,primary=true,provision=true,mode=802.3ad,attached_devices=[enp1s0f0,enp1s0f1]" \ --interface="type=interface,mac=0c:c4:74:b3:9c:ba,identifier=enp1s0f0,domain_id=1,subnet_id=11,managed=true" \ --interface="type=interface,mac=0c:c4:74:b3:9c:bb,identifier=enp1s0f1,managed=true"
1) It doesn't inherit puppet, puppet ca and realm proxy configuration from the hostgroup while it does inherit the operating system related configuration. 2) it doesn't create/modify anything under the network configuration, it leaves the IP that was handed off by the DHCP, and same with the writer of this post, it's a different range used for provisioning only. An identical "hammer" command works fine when creating a new host. $ hammer host create \ --build=1 \ --enabled=1 \ --managed=1 \ --hostgroup-id=9 \ --name="server1" \ --owner-id=4 \ --provision-method=build \ --interface="type=bond,mac=0c:c4:74:b3:9c:ba,identifier=bond0,name=server1,domain_id=1,subnet_id=11,ip=172.14.20.13,managed=true,primary=true,provision=true,mode=802.3ad,attached_devices=[enp1s0f0,enp1s0f1]" \ --interface="type=interface,mac=0c:c4:74:b3:9c:ba,identifier=enp1s0f0,domain_id=1,subnet_id=11,managed=true" \ --interface="type=interface,mac=0c:c4:74:b3:9c:bb,identifier=enp1s0f1,managed=true" On Thursday, December 8, 2016 at 4:33:26 PM UTC+2, Alexander Rilik wrote: > > Hello, > > I am testing the Discovery plugin. I have a DHCP server setup to assign a > limited range of addresses (dedicated to pxe booting hosts). The remaining > addresses are out of the DHCP scope to be permanently assigned to the > hosts. Foreman is configured to autosuggest IPs outside of the DHCP range. > I'm having this problem: > > 1. boot new host, it gets discovered > 2. open the "provision" > "interfaces" tab. The IP pre-assigned is the > one that has been provided by DHCP during PXE boot > 3. Manually change the address to an address of choice from outside > the DHCP range. This will be the real host IP > 4. Foreman throws a "DHCP records <mac>/<IP> already exists" warning > and asks me if I want to overwrite it > > Is this the expected behavior? The lease is indeed there because of the > PXE boot, so the conflict warning makes sense. > I would like foreman to let me choose whatever IP I want for the host, > instead. > The conflict error appears even when configuring the IPAM dropdown in the > subnet config to "none". > > I read a few threads dealing with the same situation but it's still not > clear to me what would be the suggested DHCP deployment scenario. > > Thank you! > > > -- 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.
