Bug #5996
open
Editing host, adding a puppet class fails with DHCP timeout error
Description
Warning!
ERF12-4395 [ProxyAPI::ProxyException]: Unable to retrieve DHCP entry for 00:50:56:00:00:00 ([RestClient::RequestTimeout]: Request Timeout) for proxy http://dhcp.fqdn:8443/dhcp
If you feel this is an error with Foreman itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries.
ProxyAPI::ProxyException ERF12-4395 [ProxyAPI::ProxyException]: Unable to retrieve DHCP entry for 00:50:56:00:00:00 ([RestClient::RequestTimeout]: Request Timeout) for proxy http://dhcp.fqdn: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/controllers/hosts_controller.rb:117:in `block in update' 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/controllers/hosts_controller.rb:109:in `update' app/models/concerns/foreman/thread_session.rb:33:in `clear_thread' lib/middleware/catch_json_parse_errors.rb:9:in `call'
Don't expect Puppet classes option editing to be affected by DHCP timeout.
Updated by Dominic Cleal almost 10 years ago
- Category set to DHCP
Generally all data associated with a host is re-validated when you save, irrespective of whether it changed. The underlying issue here is likely in the proxy.
Updated by Jon Skarpeteig almost 10 years ago
This behavior is a bit confusing, as changing the puppet class on the hostgroup rather than the host itself works fine
Updated by Jon Skarpeteig almost 10 years ago
Also worth mentioning that the foreman-proxy for the dhcp responds fine when viewing the uri in a browser.
Updated by Jon Skarpeteig almost 10 years ago
This has been identified as an IPv6 routing issue between the foreman host, and the forman proxy.