Bug #6839
closedConflict DHCP records when using the "Use Foreman Hosts Providers>Provisioned Hosts" of ovirt 3.5
Description
When using the "Use Foreman Hosts Providers>Provisioned Hosts" option from the Advanced foreman integration from oVirt 3.5 beta2 (http://wiki.ovirt.org/Features/AdvancedForemanIntegration).
The following error occurs:
Started PUT "/api/v2/discovered_hosts/mac0025904aa8c4" for 10.100.100.105 at 2014-07-30 14:27:26 +0200
Processing by Api::V2::DiscoveredHostsController#update as JSON
Parameters: {"discovered_host"=>{"name"=>"node2.testing.com", "hostgroup_id"=>"3", "environment_id"=>"1", "mac"=>"00:43:33:4a:a3:b5", "domain_id"=>"1", "subnet_id"=>"2", "ip"=>"xxx.xxx.xxx.xx", "architecture_id"=>"1", "operatingsystem_id"=>"1", "medium_id"=>"1", "ptable_id"=>"7", "root_pass"=>"[FILTERED]", "host_parameters_attributes"=>[{"name"=>"host_ovirt_id", "value"=>"[FILTERED]", "_destroy"=>"false", "nested"=>""}, {"name"=>"compute_resource_id", "value"=>"[FILTERED]", "_destroy"=>"false", "nested"=>""}, {"name"=>"pass", "value"=>"[FILTERED]", "_destroy"=>"false", "nested"=>""}, {"name"=>"management", "value"=>"[FILTERED]", "_destroy"=>"false", "nested"=>""}]}, "apiv"=>"v2", "id"=>"mac0025904aa8c4"}
Authorized user admin(Admin User)
DHCP records node2.testing.com-00:43:33:4a:a3:b5/xxx.xxx.xxx.xx already exists
Unprocessable entity Host::Discovered (id: 20):
Name has already been taken
IP address has already been taken
Conflict DHCP records node2.testing.com-00:43:33:4a:a3:b5/xxx.xxx.xxx.xx already exists
Rendered api/v2/errors/unprocessable_entity.json.rabl within api/v2/layouts/error_layout (1.3ms)
Completed 422 Unprocessable Entity in 2068ms (Views: 1.9ms | ActiveRecord: 12.4ms)
Updated by Dominic Cleal over 10 years ago
- Project changed from Foreman to Discovery
- Category changed from DHCP to Discovery plugin
Updated by Lukas Zapletal over 8 years ago
- Status changed from New to Need more information
What discovery and foreman version do you use? These conflicts were resolved in latest stable versions already. It was caused by multiple leases.
Updated by Anonymous over 7 years ago
- Status changed from Need more information to Resolved
no reaction, closing