Bug #6396
closed
an error removing a DHCP record (record doesn't exist) stops the delete process for a host
Added by David Swift almost 11 years ago.
Updated over 6 years ago.
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}}
- Status changed from New to Ready For Testing
- Target version set to 1.8.1
- Project changed from Foreman to Smart Proxy
- Category changed from Smart Proxy to DHCP
Tested so far but doesn't seem to solve the problem yet.
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.
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!
- Translation missing: en.field_release set to 18
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, 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.
- Target version changed from 1.8.1 to 1.8.0
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.
Don't worry, it wasn't that important. Thanks for checking David.
- Bugzilla link set to 1117836
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF