Bug #5637

DHCP conflicts triggered for non-conflicting leases

Added by Greg Sutcliffe over 3 years ago. Updated almost 3 years ago.

Status:Closed
Priority:Normal
Assigned To:Greg Sutcliffe
Category:DHCP
Target version:Sprint 23
Difficulty: Bugzilla link:1107707
Found in release:1.5.0 Pull request:https://github.com/theforeman/foreman/pull/1861
Story points-
Velocity based estimate-
Release1.5.1Release relationshipAuto

Description

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.


Related issues

Related to Smart Proxy - Bug #5648: DHCP lease reading is done in the wrong order Closed 05/09/2014
Related to Foreman - Bug #7971: DHCP conflict still triggered for non-conflicting leases Closed 10/16/2014
Related to Foreman - Feature #8720: Add disable_dhcp_validations global setting Rejected 12/16/2014
Duplicated by Foreman - Bug #6032: No option to overwrite DHCP option Duplicate 06/03/2014
Duplicated by Foreman - Feature #5608: Existing DHCP lease cannot be overwritten Duplicate 05/07/2014

Associated revisions

Revision 14646e77
Added by Greg Sutcliffe over 3 years ago

Fixes #5637 - Don't raise lease conflicts when reading ad-hoc DHCP leases

History

#1 Updated by Dominic Cleal over 3 years ago

  • Status changed from New to Assigned
  • Found in release set to 1.5.0

#2 Updated by Dominic Cleal over 3 years ago

  • Status changed from Assigned to Ready For Testing

#3 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #5648: DHCP lease reading is done in the wrong order added

#4 Updated by Greg Sutcliffe over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by Dominic Cleal over 3 years ago

  • Duplicated by Bug #6032: No option to overwrite DHCP option added

#6 Updated by Dominic Cleal over 3 years ago

  • Duplicated by Feature #5608: Existing DHCP lease cannot be overwritten added

#7 Updated by Bryan Kearney over 3 years ago

  • Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1107707

#8 Updated by The Foreman Bot almost 3 years ago

  • Pull request https://github.com/theforeman/foreman/pull/1861 added

#9 Updated by Lukas Zapletal almost 3 years ago

  • Related to Bug #7971: DHCP conflict still triggered for non-conflicting leases added

#10 Updated by Lukas Zapletal over 2 years ago

  • Related to Feature #8720: Add disable_dhcp_validations global setting added

Also available in: Atom PDF