Bug #6396: an error removing a DHCP record (record doesn't exist) stops the delete process for a host - Smart Proxy - Foreman

Actions

Copy link

Bug #6396

closed

an error removing a DHCP record (record doesn't exist) stops the delete process for a host

Added by David Swift over 10 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

David Swift

Category:

DHCP

Target version:

1.5.2

Difficulty:

trivial

Triaged:

Bugzilla link:

1117836

Pull request:

Fixed in Releases:

Found in Releases:

Foreman - 1.5.1

Red Hat JIRA:

Description

Trying to delete a host that does not have a DHCP record generates an error that prevents deletion of the host. The error is:

{"host":{"full_messages":["Remove DHCP Settings for our.host.com task failed with the following error: ERF12-0635 [ProxyAPI::ProxyException]: Unable to delete DHCP entry for 00:25:90:00:99:00 ([RestClient::BadRequest]: 400 Bad Request) for proxy https://our.host.com:8443/dhcp"],"errors":{"base":["Remove DHCP Settings for our.host.com task failed with the following error: ERF12-0635 [ProxyAPI::ProxyException]: Unable to delete DHCP entry for 00:25:90:00:99:00 ([RestClient::BadRequest]: 400 Bad Request) for proxy https://our.host.com:8443/dhcp"]},"id":1743}}

Actions

Copy link

Updated by Yama Kasi over 10 years ago

I have the same issue.

I also see this on the proxy log:

E, [2014-06-26T12:28:08.155374 #9147] ERROR -- : Removing a Proxy::DHCP Record which doesn't exist

This came out of the blue, see https://groups.google.com/forum/#!topic/foreman-users/JV0Zo6P248Y

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Status changed from New to Ready For Testing
Target version set to 1.8.1

https://github.com/theforeman/smart-proxy/pull/174

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Project changed from Foreman to Smart Proxy
Category changed from Smart Proxy to DHCP

Actions

Copy link

Updated by Yama Kasi over 10 years ago

Tested so far but doesn't seem to solve the problem yet.

Actions

Copy link

Updated by David Swift over 10 years ago

Yama,

Without further detail, I cannot say if this will fix your problem or not. The root cause of your issue may actually be #6412, which I just nailed down yesterday.

Actions

Copy link

Updated by Yama Kasi over 10 years ago

Hi David,

There wasn't much extra related info indeed.

Thanks btw, this other "bug" fixed it, but I wasn't awre of that one yet... I saw a lot of new reports here tho.

Thanks!

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Translation missing: en.field_release set to 18

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

David, do you still have the proxy.log from this incident? I'd just like to include it for the record & our troubleshooting docs.

Actions

Copy link

Updated by David Swift over 10 years ago

Dominic, I do have a log, with a ton of debugging I added as a temporary measure to help me narrow this down. I am out of the office this week, but I'll attach it here when I get back to work.

Actions

Copy link

#10

Updated by Anonymous over 10 years ago

Target version changed from 1.8.1 to 1.8.0

Actions

Copy link

#11

Updated by David Swift over 10 years ago

Dominic Cleal wrote:

David, do you still have the proxy.log from this incident? I'd just like to include it for the record & our troubleshooting docs.

Dominic,

Looking at the log, there is a huge amount of proprietary networking information in there. Problem is, you cannot see the bug unless the network information is consistent.

Trying to go through and replace all the IP addresses and subnets is more than I can currently do. I'll try and sanitize the log, but it is gonna take a bit.

Actions

Copy link

#12