Project

General

Profile

Actions

Support #20866

closed

Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)

Added by Christian Meißner over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Triaged:
Fixed in Releases:
Found in Releases:

Description

After update foreman und foreman-proxy to 1.15.3 we can't remove hosts.

in production.log (attached) you can find

2017-09-07T09:05:44 12b83fda [app] [W] Remove DHCP Settings for oobtest-k8smaster-1-test-01.test.domain.tld task failed with the following error: ERF12-0635 [ProxyAPI::ProxyException]: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request) for proxy https://oob-foreman-1-prod-01.domain.tld:8443/dhcp
 | ProxyAPI::ProxyException: ERF12-0635 [ProxyAPI::ProxyException]: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request) for proxy https://oob-foreman-1-prod-01.domain.tld:8443/dhcp

This bug is related to #19561. Which we also faced after upgrade. This issue can be fixed by applying the patch mentioned in the issue report.

So we can setup new hosts but never delete hosts.


Files

host_delete_error.log host_delete_error.log 35.4 KB excerpt from production.log Christian Meißner, 09/07/2017 03:23 AM
foreman-debug-2zpYH.tar.xz foreman-debug-2zpYH.tar.xz 1.06 MB Christian Meißner, 09/07/2017 03:39 AM
host_delete_error-proxy.log host_delete_error-proxy.log 25.4 KB Christian Meißner, 09/07/2017 04:41 AM
Actions #1

Updated by Lukas Zapletal over 6 years ago

  • Status changed from New to Need more information
  • Priority changed from Immediate to Normal

Hello,

please provide foreman-debug -u and tell us what DHCP provider is in use? Shall I assume Infoblox as well?

Actions #2

Updated by Christian Meißner over 6 years ago

Lukas Zapletal wrote:

Hello,

please provide foreman-debug -u and tell us what DHCP provider is in use?

See attached.

Shall I assume Infoblox as well?

Yes it's infoblox too.

Actions #3

Updated by Lukas Zapletal over 6 years ago

  • Project changed from Foreman to Smart Proxy
  • Category changed from DHCP to DHCP
  • Status changed from Need more information to New

Thanks, there were no changes in smart-proxy in 1.15.3 release at all:

https://github.com/theforeman/smart-proxy/commits/1.15-stable

But I see that in 1.15 series there were both Infoblox plugins 0.0.5 and 0.0.6. That was a rebase with number of changes:

https://github.com/theforeman/smart_proxy_dhcp_infoblox/commits/master

I will let Dmitri to analyze this, but for now I'd recommend for you to downgrade to 0.0.5 to unblock your instance. Simply downgrade the package and restart foreman-proxy that should work I think.

Actions #4

Updated by Lukas Zapletal over 6 years ago

Sorry I was informed that downgrade will not help, it's all broken in 1.15 series.

We don't test this provider that much as ISC. Hopefully we can identify the issue.

Actions #5

Updated by Lukas Zapletal over 6 years ago

One more thing, can you increase foreman-proxy verbosity to DEBUG, restart it and perform one another try. You can use foreman-tail command to extract the backtrace and debug info, pastebin the transaction. We have a report that this works, so it's perhaps some custom configuration you have.

Actions #6

Updated by Klaas D over 6 years ago

in general I'd say the 0.0.6 version of the infoblox proxy should work -- did you also update to the new infoblox 2.0 gem? Also post your infoblox smart proxy configuration (without passwords ofcause)

Actions #7

Updated by Klaas D over 6 years ago

there is one more bugfix after the 0.0.6 release: https://github.com/theforeman/smart_proxy_dhcp_infoblox/commit/80aba497ec58ad1d2e6f5c64bfc897ecde0f1546 maybe that could help

Actions #8

Updated by Christian Meißner over 6 years ago

Lukas Zapletal wrote:

One more thing, can you increase foreman-proxy verbosity to DEBUG, restart it and perform one another try. You can use foreman-tail command to extract the backtrace and debug info, pastebin the transaction. We have a report that this works, so it's perhaps some custom configuration you have.

Ok, attached you can find the excerpt from proxy.log.

Actions #9

Updated by Christian Meißner over 6 years ago

Klaas D wrote:

in general I'd say the 0.0.6 version of the infoblox proxy should work -- did you also update to the new infoblox 2.0 gem? Also post your infoblox smart proxy configuration (without passwords ofcause)

Version 0.0.6 is not available with these apt endpoints:

deb http://deb.theforeman.org/ xenial stable
deb http://deb.theforeman.org/ plugins stable

i also updated the gem

# gem update infoblox
Updating installed gems
Updating infoblox
Fetching: infoblox-2.0.5.gem (100%)
Successfully installed infoblox-2.0.5
Parsing documentation for infoblox-2.0.5
Installing ri documentation for infoblox-2.0.5
Installing darkfish documentation for infoblox-2.0.5
Done installing documentation for infoblox after 0 seconds
Parsing documentation for infoblox-2.0.5
Done installing documentation for infoblox after 0 seconds
Gems updated: infoblox
Actions #10

Updated by Christian Meißner over 6 years ago

Klaas D wrote:

there is one more bugfix after the 0.0.6 release: https://github.com/theforeman/smart_proxy_dhcp_infoblox/commit/80aba497ec58ad1d2e6f5c64bfc897ecde0f1546 maybe that could help

This commit does the trick.

Actions #11

Updated by Anonymous over 6 years ago

I released smart_proxy_dhcp_infoblox gem version 0.0.7, which includes all latest changes, today. New RPM packages should be available in a couple of days.

Actions #12

Updated by Anonymous over 6 years ago

  • Tracker changed from Bug to Support
Actions #13

Updated by Christian Meißner over 6 years ago

Dmitri Dolguikh wrote:

I released smart_proxy_dhcp_infoblox gem version 0.0.7, which includes all latest changes, today. New RPM packages should be available in a couple of days.

Hopefully new DEB packages will arrives to.

Actions #14

Updated by Anonymous over 6 years ago

  • Status changed from New to Resolved

Closing this issue. Please create a new one if the problem re-appears.

Actions

Also available in: Atom PDF