Re: [foreman-users] Re: Discovery, DHCP and lease conflict

2016-12-11 Thread Lukas Zapletal
Oh I was not aware that API provisioning is also affected by the non-inherited Puppet flags. The other one (unused_ip API is never called) is tracked under: http://projects.theforeman.org/issues/16143 We are actively working on both bugs. LZ On Fri, Dec 9, 2016 at 8:31 PM, Erez Zarum wrote:

[foreman-users] Re: Discovery, DHCP and lease conflict

2016-12-09 Thread Erez Zarum
Yes, up to now, i have not suffered from that much because so far i could set those settings manually and they were applied, but i assume in a large complex environment it could create some issues. On Friday, December 9, 2016 at 7:12:16 PM UTC+2, Alexander Rilik wrote: > > On Friday, December 9,

[foreman-users] Re: Discovery, DHCP and lease conflict

2016-12-09 Thread Alexander Rilik
On Friday, December 9, 2016 at 5:22:24 PM UTC+1, Erez Zarum wrote: > > > 1) It doesn't inherit puppet, puppet ca and realm proxy configuration from > the hostgroup while it does inherit the operating system related > configuration. > I hit this as well, but I thought it was related to the webgui

[foreman-users] Re: Discovery, DHCP and lease conflict

2016-12-09 Thread Erez Zarum
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