if an active lease (even one matching the current host data) is attempted to be provisioned, the core will raise some like this: ProxyAPI::ProxyException ERF12-4395 [ProxyAPI::ProxyException]: Unable to retrieve DHCP entry for 52:54:00:33:b5:df ([Net::LeaseConflict]: 52:54:00:33:b5:df/192.168.123.52) for proxy https://foreman.hostonly.sapphire.elysium.emeraldreverie.org:8443/dhcp lib/proxy_api/dhcp.rb:53:in `rescue in record' lib/proxy_api/dhcp.rb:43:in `record' lib/net/dhcp/record.rb:41:in `conflicts' lib/net.rb:27:in `conflicting?' app/models/concerns/orchestration/dhcp.rb:140:in `dhcp_conflict_detected?' app/models/concerns/orchestration.rb:47:in `valid?' app/models/concerns/foreman/sti.rb:29:in `save_with_type' app/models/taxonomy.rb:41:in `block in no_taxonomy_scope' app/models/taxonomy.rb:48:in `block (2 levels) in as_taxonomy' app/models/concerns/foreman/thread_session.rb:143:in `as_location' app/models/taxonomy.rb:47:in `block in as_taxonomy' app/models/concerns/foreman/thread_session.rb:108:in `as_org' app/models/taxonomy.rb:46:in `as_taxonomy' app/models/taxonomy.rb:40:in `no_taxonomy_scope' app/models/concerns/foreman/thread_session.rb:33:in `clear_thread' lib/middleware/catch_json_parse_errors.rb:9:in `call' This is due to 90ff2a3a4eaa07af0f9521468a978701cf21981f which added extra validations to the dhcp orchestration.
Created from redmine issue http://projects.theforeman.org/issues/5637
Moving to POST since upstream bug http://projects.theforeman.org/issues/5637 has been closed
Developer verified on Satellite-6.0.4-RHEL-6-20140829.0. Ran a VM which created this lease: lease 192.168.100.23 { starts 1 2014/09/01 12:52:57; ends 1 2014/09/01 13:02:57; tstp 1 2014/09/01 13:02:57; cltt 1 2014/09/01 12:52:57; binding state active; next binding state free; hardware ethernet 52:54:00:29:04:a7; } { "ip": "192.168.100.23", "starts": "Mon Sep 01 12:52:57 UTC 2014", "state": "active", "ends": "Mon Sep 01 13:02:57 UTC 2014", "mac": "52:54:00:29:04:a7", "subnet": "192.168.100.0/255.255.255.0", "tstp": "Mon Sep 01 13:02:57 UTC 2014" } Registered a new host with IP 192.168.100.23 and MAC 52:54:00:29:04:a7 without any reported conflict.
Tested with Sat6-GA-snap7 Installed Packages candlepin-0.9.23-1.el6_5.noarch candlepin-common-1.0.1-1.el6_5.noarch candlepin-scl-1-5.el6_4.noarch candlepin-scl-quartz-2.1.5-5.el6_4.noarch candlepin-scl-rhino-1.7R3-1.el6_4.noarch candlepin-scl-runtime-1-5.el6_4.noarch candlepin-selinux-0.9.23-1.el6_5.noarch candlepin-tomcat6-0.9.23-1.el6_5.noarch createrepo-0.9.9-21.2.pulp.el6sat.noarch elasticsearch-0.90.10-6.el6sat.noarch katello-1.5.0-30.el6sat.noarch katello-certs-tools-1.5.6-1.el6sat.noarch katello-default-ca-1.0-1.noarch katello-installer-0.0.64-1.el6sat.noarch katello-server-ca-1.0-1.noarch mod_wsgi-3.4-1.pulp.el6sat.x86_64 pulp-katello-0.3-4.el6sat.noarch pulp-nodes-common-2.4.1-0.5.rc1.el6sat.noarch pulp-nodes-parent-2.4.1-0.5.rc1.el6sat.noarch pulp-puppet-plugins-2.4.1-0.5.rc1.el6sat.noarch pulp-puppet-tools-2.4.1-0.5.rc1.el6sat.noarch pulp-rpm-plugins-2.4.1-0.6.beta.el6sat.noarch pulp-selinux-2.4.1-0.5.rc1.el6sat.noarch pulp-server-2.4.1-0.5.rc1.el6sat.noarch python-gofer-qpid-1.3.0-1.el6sat.noarch python-isodate-0.5.0-1.pulp.el6sat.noarch python-kombu-3.0.15-12.pulp.el6sat.noarch python-pulp-bindings-2.4.1-0.5.rc1.el6sat.noarch python-pulp-common-2.4.1-0.5.rc1.el6sat.noarch python-pulp-puppet-common-2.4.1-0.5.rc1.el6sat.noarch python-pulp-rpm-common-2.4.1-0.6.beta.el6sat.noarch python-qpid-0.22-14.el6sat.noarch python-qpid-qmf-0.22-37.el6.x86_64 qpid-cpp-client-0.22-42.el6.x86_64 qpid-cpp-server-0.22-42.el6.x86_64 qpid-cpp-server-linearstore-0.22-42.el6.x86_64 qpid-java-client-0.22-6.el6.noarch qpid-java-common-0.22-6.el6.noarch qpid-proton-c-0.7-1.el6.x86_64 qpid-qmf-0.22-37.el6.x86_64 qpid-tools-0.22-12.el6.noarch ruby193-rubygem-katello-1.5.0-86.el6sat.noarch rubygem-hammer_cli_katello-0.0.4-14.el6sat.noarch rubygem-smart_proxy_pulp-1.0.1-1.1.el6sat.noarch
This was delivered with Satellite 6.0 which was released on 10 September 2014.